Fake Address Generator

Plausible postal addresses for test forms and demos. Per-country formats (US, UK, DE, FR, CA, JP, AU).

Country
How many
Press Generate

Pick a country and hit Generate.

Test data only — these addresses don't correspond to real locations and won't receive mail.

01 — Overview

How the Fake Address Generator works

Generate realistic-looking but fully fictional addresses. Per-country formatting handles things like postcode layout, region/state codes, and street naming conventions. Use for form QA, demo seeds, and screenshots — these never resolve to real residences.

02 — Use cases

When to use the Fake Address Generator

  1. 01

    QA a shipping address form with realistic per-country input

  2. 02

    Seed an admin user table with plausible addresses

  3. 03

    Mock an order confirmation screen for a demo

  4. 04

    Test postcode validation across multiple country formats

03 — Examples

Fake Address Generator examples

1 × US address

ex 01

482 Maple Street, Apt 3B, Portland, OR 97214

US format: street + city + state + ZIP.

3 × UK addresses

ex 02

14 Birch Lane, Bristol, BS1 4HQ\n8 Park Crescent, Leeds, LS2 9JT\n...

UK format: street + town + county + postcode.

1 × German address

ex 03

Lindenstraße 47, 10969 Berlin, Germany

Postcode precedes the city, and the house number follows the street name.

1 × Japanese address

ex 04

〒150-0043 東京都渋谷区道玄坂2-11-1

Ordered largest unit first — prefecture, ward, district, block — with no street name.

04 — FAQ

Address — frequently asked questions

Are these real addresses?

No. Street numbers, names, and postcodes are recombined from realistic patterns — they're statistically plausible but don't correspond to real locations. Don't expect mail sent to them to arrive.

Do the postcodes validate?

They follow each country's postcode format (e.g. UK two-part, US 5-digit) and will pass most regex-based validators. They won't pass real lookup services like Royal Mail's PAF or USPS.

Can I use these to test an address validation API?

They'll pass format checks and fail verification, which is usually what you want from a test. Services that check against a real postal database — USPS, Loqate, Google's Address Validation — will report the address as not found. Use your provider's sandbox keys if you need a verified result.

Why do address forms break outside the US?

Because they assume a shape that isn't universal. Not every country has states, not every country has postcodes, house numbers come after the street name in some places and before it in others, and Japan orders things largest-unit-first. A required State field is the single most common way to lock out an international customer.

What's the safest schema for storing an address?

Two or three free-text lines, a locality, an optional region, an optional postal code, and a required ISO 3166 country code. Validate the postal code's format per country only if you have to, and never make region mandatory. You can always parse later; you can't recover what the form refused to accept.

Could a generated address match a real one by chance?

It's possible — street names and numbers are recombined from realistic components, so a collision isn't impossible in a dense city. Treat them as format-valid fixtures rather than guaranteed-fictional, and never use them anywhere something might physically be sent.

05 — Reference

Specs and further reading

The primary sources this tool follows. Where behaviour is defined by a specification, we link the specification rather than a summary of it.

07 — More

Tools that pair with Address

Last updated .