Free Dunkin Locations Database: 11,020 U.S. Records

Looking for a Dunkin locations list you can map, search, analyze, or import into your own project? This free database includes 11,020 U.S. location records, 18 useful fields, and matching UTF-8 CSV, JSON, and SQLite files.

Whether you are building a store map, comparing regional coverage, testing a geospatial application, researching restaurant locations, or creating a searchable directory, a structured file is far easier to use than copying results from individual web pages. The Dunkin locations list gives you consistent columns, portable formats, and enough context to decide which records fit your project.

The Dunkin Donuts Locations Database uses the July 2026 Overture Maps Places release and includes a public schema, field statistics, sample records, source information, and three ready-to-use data formats. You can examine the coverage before downloading, then choose the file that works best with your spreadsheet, database, mapping software, or application.

What is in the current release?

The database covers U.S. places identified as Dunkin branded in the source data. Every record includes a stable Overture place identifier plus WGS84 latitude and longitude coordinates. Most records also provide a street address, city, state, postal code, telephone number, and website. Operating status, category, confidence, and source details help you review the list according to the needs of your project.

• 11,020 U.S. location records ready to search, filter, map, or import
• 18 fields per record, documented in the public table schema
• 44 states and territories represented in the state field
• Complete coordinate coverage with latitude and longitude on all 11,020 records
• 10,460 distinct phone values with 4.2% of rows missing a phone
• 8,888 distinct website values with 6.6% of rows missing a website
• No duplicate location IDs in the current downloadable database

The product page shows field definitions and completeness before you download. That makes it easy to check whether the address, phone, website, coordinate, status, and source coverage matches your intended use instead of discovering important gaps after you begin building.

What fields are included in the Dunkin locations list?

Identity and brand context

overture_id gives each place a stable identifier. location_name provides the primary place name, while brand_name supplies a normalized brand when available. Use these fields to join tables, track places between updates, label map markers, or identify names that deserve a closer look.

Address and contact coverage

address, city, state, postal_code, and country let you filter locations by market and present familiar store information. phone and website add useful contact details where available. Your application can leave missing values blank or direct visitors to an official location search for confirmation.

Coordinates and category

latitude and longitude use WGS84 coordinates and appear on every record. primary_category describes the source's main place category. These fields are useful for interactive maps, nearest-location tools, distance calculations, regional density charts, and comparisons with other restaurant or retail data.

Status, confidence, and source evidence

operating_status shows the reported status, while confidence provides the Overture confidence score. source_datasets, source_licenses, and source_update_times help you understand where a record came from and how recently its contributing information was updated.

Ways to use a Dunkin store locations database

The same Dunkin location data can support a quick spreadsheet analysis, a public map, a market-research project, or the foundation of a custom application. Start with the question you want to answer, then keep only the fields and locations that help answer it.

• Interactive maps and directories: create a searchable map, regional directory, travel-planning layer, or internal reference tool.
• Market coverage analysis: compare location density by state, city, postal code, or a radius around another set of coordinates.
• Site-selection research: use Dunkin places as one competitive or complementary layer alongside population, traffic, retail, restaurant, or property data.
• Data engineering practice: test ingestion, normalization, geospatial indexing, deduplication, API design, or database conversion with a recognizable real-world subject.
• Local publishing: research regional coverage, location patterns, or travel resources while linking readers back to current official store information.
• Data cleanup and enrichment: compare completeness, confidence, operating status, and source dates before combining the records with another business or geographic dataset.

Choose the format that matches the work

The protected download delivers the same accepted records in three working formats. UTF-8 CSV is convenient for spreadsheets, imports, dataframes, and broad tool compatibility. JSON fits application code, document-oriented workflows, and API prototypes. SQLite provides a portable relational database that can be queried immediately without configuring a database server.

All three formats contain the same 11,020 records, so you can switch tools without changing the underlying list. The included schema, sample, statistics, README, license, and manifest explain the fields and make the database easier to share with collaborators.

Important notes before using the locations

This is a research and development resource, not the official Dunkin store locator and not an email marketing list. Restaurant and retail locations change continually. A store may open, close, move, change its phone number, share an address with another concept, or appear under a source-provided name that needs additional review.

The source-reported operating_status and confidence score are useful evidence, but neither replaces confirmation for a consequential decision. If someone is about to travel, place an order, sign a lease, contact a franchise, or publish a claim about a specific store, verify that location through the official brand site or another current primary source.

Use the published field statistics to plan for missing phone numbers, websites, or other optional values. When a specific location affects travel, purchasing, outreach, publishing, or another important decision, confirm it with the official Dunkin website or another current primary source.

How to get better results from the database

1. Inspect before downloading. Read the schema, field statistics, coverage note, and sample records on the product page.
2. Define the question. Decide whether the project needs mapping, counts, contact coverage, proximity, enrichment, or another measurable output.
3. Filter deliberately. Apply operating-status, confidence, completeness, geography, and category rules that fit the use case.
4. Keep stable identifiers. Retain overture_id and the source fields so you can compare locations and review questionable matches later.
5. Validate consequential results. Confirm individual locations through current primary sources before acting on them.
6. Document the release. Retain the version, README, schema, license, and manifest with any derived work.

A more useful Dunkin location resource

The original 2011 download was a simple list created for a short-lived developer challenge. This edition is designed for the way people use location data now: clear columns, coordinates on every record, multiple portable formats, field-level coverage statistics, sample records, and documentation that travels with the files.

If you arrived looking for a Dunkin locations database, a Dunkin store list in CSV, U.S. Dunkin coordinates, or free restaurant location data for a project, the product page gives you the important answers in one place. You can inspect the columns, view sample data, compare field coverage, and download the same records as CSV, JSON, or SQLite.