Address Parser & Formatter

Reproducible tool walkthroughs

These examples run synthetic inputs through the current tool rules. They are not customer studies, real orders, or delivery checks. 2026-09-07.2

3. Structured parsing and uncertain input

Leave country detection on automatic, paste this text, and select Parse address. Open tool

Altmarkt 1
01067 Dresden
Germany

Actual mailing-label output:

Altmarkt 1
01067 Dresden
Germany

Then enter Building C near the station. Actual confidence is low. The parser preserves uncertain text. Supply the country and fields manually; parsing confidence does not establish address existence.

Download this version's examples and full inputs/results: CSV · JSON · Settings · Full results

Release notes: this version corrects German address order, country-specific postal boundaries, optional UK/German region fields, and Japanese postal normalization. CSV no longer writes formulas. An old seed can produce different data after an update; retain your exported files.

Rule references: Deutsche Post addressing FAQ · Royal Mail: optional county information · Data and editorial standards

Use cases

• Turn copied synthetic address text into street, locality, region, postal-code, and country fields for form and import testing.
• Review which values were extracted confidently and which fields or unmatched lines still require a human decision.
• Convert reviewed fields into a single line, mailing-label layout, JSON object, or CSV row without retyping the address.
• Test how international address ordering, Unicode, postcode placement, and regions without postal codes interact with a target schema.

Address format notes

• Parsing uses conservative browser-local rules and preserves text that cannot be assigned confidently; pasted values are not uploaded to AddressLab.
• Users can edit every extracted field before copying output, and manually supplied corrections replace uncertainty rather than pretending the parser knew the answer.
• Formatting does not establish existence, ownership, official postal assignment, geocoding accuracy, or deliverability.

How conservative address parsing works

The parser first normalizes whitespace, then looks for an explicit country and maintained postal syntax. It assigns only fields supported by recognizable structure. Ambiguous lines remain in an unmatched section, while missing or uncertain fields are labeled for review instead of being completed from guesses.

Parsing confidence is not address validation

High parsing confidence means that several pieces of text matched a maintained structural rule. It says nothing about whether a building exists, who occupies it, whether a postcode is currently assigned, or whether a carrier will deliver there. Production data still needs recipient confirmation or an appropriate validation provider.

Address-to-JSON walkthrough

Load the synthetic US example and parse it. Review the five extracted fields, make any correction in the editable controls, and copy the JSON output. The same reviewed fields also produce the single-line, mailing-label, and CSV-row variants, which helps compare representations during form, API, and import QA.

Handling ambiguous and international input

If the country is missing, the parser may suggest Canada, the UK, or Japan only when distinctive postal syntax is present. Otherwise it asks for a country hint. Japanese ordering and Hong Kong's normal lack of a postcode are handled separately from Western city-region-postcode layouts.

FAQ