⌘ K
fake phones · 6 countries · e.164-ish · local

Generate fake phone numbers

Country-formatted fake phone numbers for QA fixtures and form validation. US uses the reserved 555 prefix; other countries follow national mobile patterns.

Fake Phone Number Generator
Numbers
0
50 requested
Country
US
(+1)
Format
E.164-ish
national mobile
Output
0 B
txt
CountryCount 50
input · format reference

National-style fake mobile numbers with country prefix.

  • US (+1 555 …) — reserved test prefix, never dial.
  • UK (+44 7… mobile), India (+91 9…), Germany (+49 1…).
  • France (+33 6 …), Japan (+81 90 …).
output · numbers (0)

Click Generate to produce fake phone numbers

Quick Start

How fake phone numbers work

Each country has a country code prefix, mobile-block prefix, and remaining digits. We follow national mobile patterns so address-book apps accept them.

  1. 01

    Pick a country

    US, UK, India, Germany, France, or Japan.

    Inputs are treated as UTF-8 throughout the pipeline and validated client-side as you type — nothing dispatches until the value is well-formed.

    countryinpututf-8client-sidevalidated
    country · textUS · set
    +1 555 …
    loaded · parsedclient-side
  2. 02

    Choose count

    1 to 1000 numbers per batch.

    Each toggle re-computes through a memoised hook, so flipping options never resets your input and the UI stays snappy on large inputs.

    countoptionslivememoisedtoggles
    count · memoised50 · live
    50 numbers
    options set · memoisedlive
  3. 03

    Generate

    Random digits fill the national-format template.

    Randomness — where used — comes from crypto.getRandomValues, never Math.random. Heavy work sits in useMemo.

    mintcomputeinstantlocaldeterministic
    mint · instantformat · computed
    +1 555 213 4567
    computed · instantinstant
  4. 04

    Copy or download

    Drop into form-validation tests or CSV imports.

    Copy writes through navigator.clipboard and downloads use a Blob — zero network traffic. Same input plus same options always yield the same bytes.

    exportcopydownloadzero-networkreproducible
    ok · copiedready · copied
    Copied
    shipped · ready to shipsuccess
Pro tips

Pro tips for everyday utilities

Reach for crypto.getRandomValues

Cryptographically random for IDs, tokens, salts. Math.random is for animation and games, not security.

Sort IDs lexicographically

UUID v4 has no time ordering. Use ULID or UUID v7 if you need sorted IDs.

Mock data with seeds

Faker-style libraries can be seeded so tests are reproducible. Embed the seed in the fixture file.

Reference cards beat memory

Cheatsheets for Vim, Git, Docker, Linux signals are faster than man pages when you’re mid-flow.

Browser APIs vary

Touch events, gamepads, and clipboard differ across vendors. Feature-detect before use.

Persist in the right place

localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data.

Related toolsFake NamesFake EmailsFake AddressesFake ProfilesMock CSVMock Data
Use Cases

When to fake phone numbers

Form tests, CSV imports, demos.

Form validation

Bulk numbers stress-test phone regex and parsers. Random values come from crypto.getRandomValues — cryptographically secure for tokens, salts, and session IDs. Math.random is deterministic enough for animations but predictable enough to be a security bug.

CSPRNG-backed

International QA

Verify libphonenumber-style libraries across countries. Pair with hashids, ULID, or UUID v7 when you need both random and sortable — useful for primary keys, public-facing IDs, and event log ordering without a sequence column.

i18n

Database seeding

Fill user records with realistic-looking phones. Output is deterministic given the same seed, so fixtures and tests stay reproducible across CI runs and contributor machines. Embed the seed in the fixture file for full replay.

snappy

Demo screenshots

Beat "555-1234" placeholders in marketing screens. Heavy work runs through useMemo so the UI stays snappy on large inputs. Same input + same options yields identical bytes — the kind of stability snapshot tests rely on.

feature-detected

OCR tests

Validate phone extraction from images. Storage tools persist to the right backend: localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data. Pick the right shelf and quota worries disappear.

deterministic

CRM imports

Generate bulk records to test import flows. Browser feature detection: clipboard, fullscreen, gamepad, and Web Bluetooth APIs gracefully fall back when unavailable. No surprise white screens on Safari or older Firefox.

production-ready
FAQ

Frequently asked questions

US numbers use 555 — reserved for fiction and never dial. Other countries use plausible patterns; numbers may coincidentally belong to real subscribers — do not dial.
Each format hand-coded. Open a PR to add more — happy to merge correct national patterns.
Mostly — the structure is realistic but specific exchange ranges may not pass strict carrier validation.
No — this only generates new ones. Use a libphonenumber wrapper for re-formatting.
Yes — numbers are built in your browser with crypto randomness. Nothing is sent to a server.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!