Random Brazilian Address Generator

Brazilian addresses: anatomy and mock data

A Brazilian residential address follows a strict order that is worth memorizing if you ship anything to or from the country: logradouro + número + complemento + bairro + cidade - UF + CEP. Logradouro is the street type and name; número is the house number; complemento is the apartment, block or floor detail; bairro is the neighborhood (a load-bearing field, unlike US ZIP codes); UF is the two-letter state code; CEP is the 8-digit postal code formatted as XXXXX-XXX. Skipping the neighborhood or formatting the CEP without the dash will break most delivery systems and several federal forms.

Brazil covers 8.5 million km² across 5,570 municipalities and 26 states plus the Federal District, with roughly 150,000 unique logradouros registered in the IBGE's CNEFE (Cadastro Nacional de Endereços para Fins Estatísticos). Any realistic mock generator has to keep CEP, city and state internally consistent — a CEP of 01310-100 belongs to Avenida Paulista in São Paulo and cannot appear next to "Manaus, AM" without breaking integrity checks.

Types of logradouro and edge cases

• Rua (~65% of all entries) and Avenida (~15%) are the dominant types.
• Alameda, Travessa, Beco, Largo, Praça, Vila, Estrada, Rodovia (BR-101, SP-070), Viaduto and Conjunto Habitacional are common variants.
• S/N ("sem número") is valid for rural and institutional addresses with no street number.
• KM 10 replaces a house number on highway addresses.
• Complemento values include Apto 502, Bloco B Apto 12, Casa, Térreo, Fundos, Loja 1.
• Favelas often use alternative numbering — numbered becos, sub-numbers like 123A, 123 fundos — which most generic mock generators ignore.

Validating that mock addresses look real

Two free APIs let you sanity-check the output. ViaCEP (viacep.com.br/ws/{cep}/json/) returns the canonical logradouro, bairro, cidade and UF for any real CEP — useful for catching CEP-vs-state mismatches in fake data. BrasilAPI exposes the same data with extra metadata. For geocoding to lat/long you can use OpenStreetMap Nominatim, Google Maps or Mapbox; the latter two cost money but understand Brazilian colloquial addresses better. For very large batches, IBGE's CNEFE dump (free, around 5 GB CSV) gives you every registered address as ground truth.

Use cases for fake Brazilian addresses

Mock addresses are useful for seeding e-commerce delivery tests, populating CRM staging environments, validating address forms (including the auto-complete from CEP that most Brazilian e-commerces ship), running load tests on shipping calculators (Correios, Loggi, Jadlog, Mercado Envios) and stress-testing fraud rules. Under the LGPD a real residential address counts as personal data with attribution risk, so generating synthetic addresses is the safer pattern for any non-production environment. Just remember that synthetic does not mean "anything goes": CEP-city-UF consistency is a hard requirement for realistic load testing.

FAQ

Can I use these addresses to test delivery integrations?

For shipping calculation (price and ETA based on CEP-to-CEP), yes — the generated CEP is valid in format and matches a real city, so calculators will respond. For actual delivery, no: the street number and complemento are random and the package will never arrive. Use a sandbox endpoint instead.

Are rural addresses supported?

The generator includes rural patterns like S/N, KM markers and Sítio/Fazenda names where appropriate. Rural CEPs in Brazil often end in -000 and correspond to an entire town rather than a specific street.

How do I make sure the CEP matches the UF?

CEP prefixes in Brazil follow geographic regions — 0xxxx for São Paulo capital, 2xxxx for Rio de Janeiro, 5xxxx for Pernambuco, and so on. This generator pins the CEP region to the chosen UF so combinations stay coherent. For extra safety, run the result through ViaCEP.

Is generating fake personal data legal under LGPD?

Synthetic data with no link to a real person falls outside the LGPD's definition of personal data. Mock addresses generated here are safe for testing and demos — what triggers LGPD is reusing real addresses scraped from leaks or real customer databases.