Spain Address Generator

What is a Spain address generator?

A Spain address generator produces synthetic, format-valid Spanish addresses and test profiles for QA, form validation, checkout testing, demos, and database seed data. All records are fictitious and do not represent a real person or address.

Each record pairs a real Spanish municipality with a five-digit postal code that belongs to its province and a +34 phone number, so the data is geographically consistent while remaining synthetic.

Common use cases

• QA testingFeed varied, format-valid addresses into manual and automated test runs so you can exercise edge cases without touching production or real customer data.
• Form validationCheck that your address, postal code, and phone inputs accept valid local formats and reject malformed ones, across every country your product supports.
• Checkout testingPopulate billing and shipping forms with consistent test records to verify tax, shipping, and address-verification logic end to end in staging.
• Software demosFill dashboards, CRMs, and admin tables with believable but fictitious records so screenshots and live demos look realistic without exposing anyone's data.
• Database seed dataSeed development and staging databases with structured records as JSON or CSV, then re-run the same import as part of your fixtures or migrations.
• Localization testingValidate that your UI renders region-specific address layouts, character sets, and postal-code shapes correctly when you switch locales.

Spain address format

Spanish addresses lead with the street type and name followed by the number, often with a floor and door — for example Calle Mayor 12, 3º B. The postal line then lists the five-digit code, the municipality, and the province.

The five-digit postal code's first two digits identify the province (28 for Madrid, 08 for Barcelona), so the postal code, city, and province always agree. The optional floor (piso) and door (puerta) parts make Spanish data useful for testing multi-part street lines.

• StreetStreet type and name then number (Calle … 12)
• Floor / DoorOptional piso and puerta (3º B)
• Postal codeFive digits; first two map to the province
• Municipality + ProvinceCity and province name
• Phone+34 with a province-appropriate prefix

What the sample set includes

The examples below keep city, comunidad, código postal, street, and phone fields in the same address set, so you can check whether forms, checkout flows, imports, and QA scripts handle those field combinations correctly.

• Cities in the sample setCiudad Lineal, Carabanchel, Las Palmas de Gran Canaria, Valencia, Alicante, Fuencarral, Hospitalet de Llobregat, Elche, Málaga, Palma de Mallorca
• Comunidad valuesComunidad Autónoma de Madrid, Comunidad Autónoma de Canarias, Comunidad Valenciana, Comunidad Autónoma de Cataluña, Andalucía, Comunidad Autónoma de las Islas Baleares, Principado de Asturias
• Código postal examples28087, 28013, 35071, 46005, 03139, 28035, 08080, 03330
• Phone prefixes shown+34 91, +34 928, +34 96, +34 95, +34 971, +34 985
• Street-name examplesCALLE BURGO DE OSMA, CALLE CLARISAS, CALLE LUIS VERDE, CALLE VERGE DEL CARME, PARTIDA BOQUERES POLIG J, CALLE BASCONES, CALLE RIERA D'EN BASTER, CALLE VIRGEN DEL CARMEN
• Street data sourcesopenaddresses

QA checklist for Spain address data

• Código postal should be stored as textCódigo postal values can contain leading zeroes, letters, spaces, or hyphens depending on the country. Treat them as strings in validation, exports, and database seed files.
• Validate the whole address combinationTest the city, comunidad, código postal, and phone prefix together. For example, this page can produce Ciudad Lineal, Comunidad Autónoma de Madrid, 28087, and +34 91 595 7453.
• Do not require fields the country does not useKeep optional fields such as county, building, unit, or address line 2 separate from required fields. A valid Spain test record should not fail because an optional local field is absent.
• Separate display format from storageDisplay the address in local order for users, but store atomic fields such as street, city, Comunidad, and código postal separately so search, shipping, and tax logic can work reliably.

Fields included

• Full nameA synthetic person name appropriate to the locale.
• Street addressHouse/building number plus street, drawn from real geographic data with a randomized number.
• CityA real city or district within the selected region.
• Region / state / prefectureThe first-level administrative division for the country (state, province, prefecture, etc.).
• Postal codeA postal/ZIP code that belongs to the selected city, in the correct local format.
• CountryThe selected country or region the record belongs to.
• Phone numberA region-matched phone number using a valid local prefix or area code.
• EmailA synthetic, non-routable email address for form testing.
• CompanyA fictitious company name for B2B and employment fields.
• UsernameA derived handle suitable for account-signup form tests.

JSON exports keep these as nested keys (for API mocks and fixtures); CSV exports flatten them into one column per field (for spreadsheets and database seed scripts).

Example generated data

A synthetic example record (not a real address):

{
  "fullName": "Micaela Medina Bravo",
  "street": "CALLE BURGO DE OSMA 251",
  "city": "Ciudad Lineal",
  "region": "Comunidad Autónoma de Madrid",
  "postalCode": "28087",
  "country": "Spain",
  "email": "micaelamedinab87@proton.me",
  "company": "Altamirano Chacón Cotto Tapia S.A."
}

Export synthetic address data

Every generated record can be exported as JSON or CSV so it drops straight into your workflow. JSON keeps the full nested structure for API mocks, fixtures, and request bodies; CSV gives you flat columns for spreadsheets, bulk imports, and database seed scripts.

Because the data is synthetic and structurally consistent, it is safe to commit export files to test repositories, load them into staging databases, or replay them in automated suites. Re-run the generator any time you need a fresh batch.

Responsible use

• All generated data is synthetic and does not describe a real person, household, or account.
• Do not use it for fraud.
• Do not use it for identity verification.
• Do not use it for payment verification.
• Do not use it to impersonate real people.
• Use it only for testing, QA, demos, development, and education.