4516 River Blvd
Boston, MA 02101
Boston, MA 02101
3594 Lake Ct
Philadelphia, PA 19101
Philadelphia, PA 19101
9233 Park St
Phoenix, AZ 85001
Phoenix, AZ 85001
8536 Meadow Ave
Portland, OR 97201
Portland, OR 97201
2790 Cedar Ave
Austin, TX 73301
Austin, TX 73301
How to use
01
Pick a batch size
Enter a number from 1 to 50 in the How many field. Five is the default, plenty for a quick form check; max it out when a table needs seeding.
02
Regenerate until it fits
Click Regenerate to reroll the entire batch. Each card shows a two line entry, street address on top, then city, state, and ZIP in standard US order.
03
Copy what you need
Every card has its own copy button for grabbing one entry, or use Copy all to export the full batch with a blank line between each address.
Why Fake Address Generator
- Generate plausible-looking fake US addresses.
- Real city + state + zip combos from 15 metro areas.
- For testing forms and shipping flows only, these don't map to real homes.
Common questions
Are these fake addresses actually deliverable?
No, and that's deliberate. The street number and name are invented, so entries pass format checks but fail USPS delivery point validation. That's the right property for test fixtures: realistic enough for your forms, useless for sending anything.
What are the generated addresses meant to be used for?
QA on address forms, seeding development databases, populating demo screenshots, and load testing checkout flows. They should never be entered anywhere a real person, carrier, or verification service will act on them.
Which cities supply the test address data?
Fifteen US metros, including New York, Los Angeles, Chicago, Houston, Austin, Seattle, Denver, Boston, and Atlanta. Each entry pulls a matching city, state, and ZIP as one unit, so the geography inside every address is internally consistent.
Will the fake addresses pass my form's ZIP validation?
Yes, for format-level rules. The ZIP is a real code belonging to the listed state, so five digit regexes and state-to-ZIP consistency checks both pass. Only services that verify a specific deliverable street will reject them, by design.
Can this produce addresses for countries outside the US?
Not currently; output follows the US pattern of street, city, state, ZIP. For UK postcodes, Japanese ordering, or other international layouts, build a small hand-made fixture set for each target country instead.
Why shouldn't I just test with real customer addresses?
A postal address is personal data under GDPR, CCPA, and most privacy regimes, and copies multiply fast across tickets, screenshots, and database dumps. Synthetic entries exercise the identical code paths with none of that exposure.
How is each random street address constructed?
A number between 100 and 9999, one of 20 common street names like Oak, Cedar, or Highland, and one of 9 suffixes such as St, Ave, or Blvd. That yields thousands of street lines, paired randomly against the metro list.