Fake UK address generator

How the UK random address generator works

This fake UK address generator builds sample British addresses for forms and fixtures. A result looks like 18 High Street, Bristol, BS8 1QU: a street, a town, and a postcode with an outward code, a space, and an inward code. It is test data, not a place to send post. Choose a quantity, press Generate, then copy fields or whole blocks — privately in your browser.

1. Select country and quantity

   Default to the United Kingdom, or switch to the United States. Pick up to 500 addresses in one run.

2. Sample from a 5,000 UK pool

   Each result draws from a prepared list of 5,000 UK-style addresses with streets, towns, counties or regions, postcodes, and phone numbers.

3. Review structured fields

   Output includes street, city, state/province/area, phone, postcode, country calling code (+44), and country.

4. Copy what you need

   Copy a single field, one full address, or every generated result with Copy all.

Who this generator is for

• Developers filling UK checkout and delivery forms
• QA teams creating British test fixtures without real PII
• Designers mocking UK address layouts in UI prototypes
• Anyone who needs quick fake UK addresses in the browser

Related tools

• US random address generator — fake United States addresses with the same shared generator
• Random number generator — unique integers for IDs, raffles, and samples

What a generated UK address contains

Each row is a synthetic United Kingdom address for tests and sample screens: a street line, a city or town, a county where the layout includes one, a postcode, and a phone-style number with a +44 calling code. The fields are there so a UK form, a validator, or a demo has realistic-looking input. They do not identify a resident. They are not proof of address. They are not a KYC document. Use them in development and in fixtures. Do not use them to open an account, pass a check, redirect mail, or present a false identity to anyone.

UK postcodes mix letters and numbers and often include a space before the final three characters. A validator written for a five-digit ZIP will reject a valid postcode shape, which is a reason to test with these rows instead of with US samples. County is not the same fact as a US state, and some modern addresses are used without leaning on the county line. Map the generated columns onto your schema deliberately. Drop county if your form has no such field. Do not stuff the postcode into a ZIP column and hope the regex was written loosely.

How this differs from the US generator

The US generator emits state, ZIP, and a +1 phone style. It is the fixture for American forms. This page is the fixture for British forms. A checkout that switches country should switch the sample, not only the label on the button. Postcodes that contain letters, phone numbers that start with a trunk digit or a +44 country code, and city names that do not match a US state list are the cases a US-only fixture never sees. Run both generators when both countries ship. Keep the assertions separate so a UK postcode is not required to match a ZIP pattern.

Neither page looks up the Royal Mail or the USPS, and neither promises that a building exists or that post will be delivered. A well-formed postcode shape can still be unassigned. That is the correct behavior for a synthetic row and the wrong behavior for a letter you actually send. Use a real address you are allowed to publish when the test is about delivery. Use these rows when the test is about parsing and display.

Batches, postcode shape, and phones

Generate one row to eyeball a form or a batch to fill a table, up to the limit on the tool. Copy a single field when a unit test needs only the postcode, or copy the block when a manual tester is walking through checkout. Do not assert the full string of a freshly generated row in a test that must stay green. Assert the shape: letters and digits in the postcode, a non-empty town, a +44 prefix if your formatter keeps it. Freeze a handful of rows in the repository when the screenshot or the contract test needs identical text every run.

Phone samples are not allocated numbers. Do not text them and do not connect them to a live telephony test. If your formatter strips the leading zero from a national number and stores E.164, run that formatter on the sample and assert the stored shape. The generator’s job ends at a plausible display value. Normalization belongs to your code, and the sample is only the input.

Formatting the line the way a UK form expects

A common UK layout is the building number and street, then the town, then the postcode, with county optional. Your form may collapse those into different boxes. Map the generated pieces explicitly rather than pasting the whole block into the street field. A postcode that lands in the city box will fail a later letter-and-digit check and send you looking for a bug in the generator. The generator’s job was to produce the parts. The assignment of parts is yours. Keep a frozen example in the test so the mapping cannot drift when someone regenerates the screenshot.

International checkout flows often show the UK fields only after the country changes. Test that transition with a generated row, then switch the country to the United States and fill the US generator’s row. The point is that the two shapes are not interchangeable. A single regex named postal code will be wrong for one of them. Write the two patterns down next to the two tools, and keep the sample data labeled so a later reader does not mail the fictional postcode.

Postcodes, counties, and outward codes

A UK postcode has an outward code and an inward code. The inward code is the final three characters, and a space often separates the two parts. Validators that demand five digits, or that strip every space and then require a fixed length, will reject legitimate shapes. Paste a generated postcode into your field and into a second field that removes the space, and decide which storage form you actually want. County is optional in many modern layouts. If your schema requires county, confirm the generated line has one before you assert it. If your schema has no county, do not fail the import because the sample included a column you do not store.

Town names and postcodes should be tested as text, not as a closed list of cities you copied from one region. A dropdown of ten cities will not accept a generated town, and that failure is the dropdown, not the address. Phone values with a +44 prefix check whether your input allows a country code. National formats that start with 0 are a separate case you can type by hand if the generator’s display keeps the international prefix. Neither case is a live number. Do not route them to a telephony provider.

Screenshots and the boundary of fake data

Public docs should not show a customer’s real address. A synthetic UK row is a reasonable stand-in when it is labeled as sample data. It is not reasonable as a supporting document, a proof of funds address, or a way to satisfy a landlord or a bank. Those uses are deceptive even when the line was produced by a randomizer. Discard any row you recognize as a real person’s home. The tool does not search for people, and a chance resemblance is still a reason to regenerate.

Integer sample IDs belong on the random number generator. US forms belong on the US address generator. This page stays specific so a UK postcode is explained as a postcode, not as a ZIP with extra letters. When the product adds another country, add fixtures for that country’s format rather than stretching this one. A generator that claims every country and teaches none of the formats will not catch the bug you are trying to catch.

UK random address generator FAQs