Download postcode data and postal code database files by country in CSV, XLSX and JSON, with city, region, administrative hierarchy and WGS84 coordinate fields for address validation, logistics and analytics.
This page is backed by structured postal records, canonical hierarchy links and representative examples from the current database. The canonical route for this record set is /datasets.
CSV is the safest default for databases and ETL jobs because postal codes must remain text.
Country exports include WGS84 latitude and longitude when coordinate coverage is available.
Jump directly into country hubs that combine postal code lookup, regional navigation and export links in one place.
Start with high-coverage country files and choose the format that matches your workflow. CSV is best for pipelines, XLSX for manual QA and JSON for application caches or service-side lookup tables.
| Country dataset | Records | Postal codes | Geocoded | Downloads |
|---|---|---|---|---|
|
Portugal
Example 1000-001 in 4 Águas
|
206,942 | 197,772 | 100.0% | |
|
United Arab Emirates
Example 00004 62392 in Abu Hail
|
178,171 | 178,171 | 100.0% | |
|
India
Example 110001 in (Gandhinagar) Sector 16
|
155,570 | 19,238 | 100.0% | |
|
Japan
Example 001-0000 in -18.20-22.24-26.32.287.300-Banchi)
|
146,883 | 142,577 | 100.0% | |
|
Mexico
Example 01000 in 1 de Diciembre
|
144,655 | 32,448 | 100.0% | |
|
Singapore
Example 018906 in Abingdon Road
|
121,154 | 121,135 | 100.0% | |
|
Peru
Example 01000 in 02 de Febrero
|
96,943 | 2,669 | 100.0% | |
|
Indonesia
Example 10110 in 1 Ilir
|
81,058 | 8,266 | 100.0% | |
|
Poland
Example 00-002 in Abisynia
|
72,900 | 20,299 | 100.0% | |
|
France
Example 01000 in Aast
|
51,611 | 20,418 | 100.0% | |
|
Russian Federation
Example 101000 in 10 Лет Октября
|
43,538 | 43,538 | 100.0% | |
|
United States
Example 00501 in APO AA
|
41,489 | 41,487 | 100.0% |
The download buttons mint a same-origin token before starting the file, so direct hotlinking is blocked while normal browser downloads remain available.
The catalog is organized by country so each download stays small enough to audit, cache and import without forcing a global file into every workflow. The current public registry exposes 1,827,156 postal records across 123 countries and territories.
Example: the Portugal dataset contains 206,942 records, 197,772 distinct postal identifiers and 22,004 mapped localities.
To support different technical architectures, country datasets are available in practical export formats for review, testing and integration. No proprietary software is required for access.
UTF-8 encoded files optimized for bulk imports and custom script processing. Universal compatibility.
Direct access for analysts using spreadsheet applications with pre-formatted columns. Ideal for manual data review.
Ready-to-deploy relational database files with optimized indices and schema. Instant backend integration.
Machine-readable nested objects designed for real-time web application consumption and NoSQL storage.
Postal-code systems vary sharply by country. The dataset is intended for lookup, testing, education, geospatial examples and data-quality workflows, not as an official delivery database. For shipping, compliance or address-certification decisions, validate against the relevant national postal authority.
These country files are good starting points for validating the schema because they include many regions, repeated postal prefixes and enough locality variation to test imports, deduplication and map display.
For production systems, import one country at a time and keep the postal identifier as text. Many countries use leading zeroes, embedded spaces or alphanumeric patterns, so integer conversion can corrupt valid codes.
Use CSV for pipelines and warehouses, XLSX for manual review, and JSON when a service needs to embed postal records directly into a search index or validation cache. The same country pages link back to the browseable hierarchy, making it possible to inspect a suspicious import row in the public UI.
| Column | Use | Import note |
|---|---|---|
| postal_code | User-facing postal identifier | Store as text, never as integer. |
| place_name | City, town or locality label | Keep UTF-8 accents and local spelling. |
| admin_name1..3 | Administrative hierarchy | Use for filtering, breadcrumbs and deduplication. |
| latitude / longitude | Map centroid or approximate locality coordinate | Treat as centroids, not delivery-point coordinates. |
The datasets provided by Postalcodes.info are engineered for high-stakes environments where accuracy is paramount. From Logistics & Supply Chain optimization, ensuring last-mile delivery precision, to Fintech & Anti-Fraud systems requiring rigorous address verification (KYC/AML).
Academic & Demographic Research: Our normalized schema allows for seamless cross-border analysis, enabling researchers to map socio-economic data against standardized administrative boundaries without spending cycles on data cleaning.
Choose the format based on the system that will consume the data. CSV is the safest default for warehouses, ETL jobs and command-line tools. XLSX is better for manual inspection and business users. JSON is useful when the file will be embedded into a service cache, search index or test fixture.
For address validation, download the country you need and build a local lookup keyed by country code and postal code. For geographic analysis, keep administrative levels and coordinates together so every point can be grouped by region, province or municipality without a second geocoding pass.
Best for bulk imports, SQL loaders and repeatable data pipelines.
Best for human review, QA checks and one-off spreadsheet analysis.
Best for application caches, tests and service-side enrichment.
Each country file includes the country code, postal code, place name, administrative levels and WGS84 latitude and longitude when coordinates are available. The same fields are used across countries so imports can share one schema.
Use CSV for repeatable database loads and ETL jobs, XLSX for manual review, and JSON for application caches, service fixtures and server-side lookup tables.
No. Store postal codes as text. Valid codes can start with zero, contain spaces, use letters or follow country-specific punctuation rules that numeric columns cannot preserve.
Access to global postal datasets. Includes ZIP codes, city names, administrative divisions, and GPS coordinates for over 190 nations. Designed for developers and GIS professionals requiring high-availability geospatial metadata.