Phone number formatter

Make phone-number formatting predictable.

Data workspace

Ready in this tab

Source

0 B Processed locally
Import settingsAuto-detect enabled
JSON text

Overrides apply on the next analysis. File decoding and every transform run only in this tab.

Paste data or choose a file to begin.

Analysis results

Analysis canvas

Ready when you are.

  1. Add a local file or paste data.
  2. Analyze format, quality, and likely sensitive fields.
  3. Review, clean, and export the in-tab working copy.
01 / Parse

Know the shape of the data.

Detect delimiters, validate structured text, and surface useful error locations.

02 / Review

Spot quality and privacy risks.

Measure completeness, duplicates, mixed values, and likely identifiers before sharing.

03 / Prepare

Shape a working copy locally.

Filter, sort, select, rename, deduplicate by keys, validate schemas, and export without changing the original file.

Focused utilities

Start with the job in front of you.

Every route opens the same private engine with guidance tailored to that format.

Practical guide

Use a country rule instead of a formatting guess

Local numbers are ambiguous without context. The formatter uses the selected country only when an international calling code is absent and reports values that do not match the supported national length.

  • 01Analyze the dataset and select the phone-number column.
  • 02Choose United States, Canada, United Kingdom, or Australia as the default country.
  • 03Compare E.164, national, international, or digits-only output in the preview.
  • 04Keep or blank invalid values, then apply the reversible change.
Which countries are supported for national formatting?

The first release supports United States, Canada, United Kingdom, and Australia rules. International numbers for other countries can be preserved as E.164 or digits-only values when they already include a plus-prefixed calling code.

Does formatting prove that a phone number is active?

No. Formatting checks a conservative digit pattern and selected country length; it does not contact the number, verify ownership, or prove that the number can receive calls.

Does Parse The Data upload my files?

No. Parsing, profiling, cleanup, and export run inside your browser tab. The application does not send dataset contents to our server or any third party.

What file types are supported?

CSV, TSV, JSON, and JSON Lines (JSONL or NDJSON) are supported as pasted text or local files up to 10 MB. CSV files can also be decoded as UTF-8, UTF-16, or Windows-1252.

Can it detect every privacy risk?

No. The privacy scan uses deterministic patterns and column-name hints. It can find common emails, phone numbers, IP addresses, SSNs, and payment-card patterns, but it is not a substitute for a formal privacy review.

Designed for restraint

The server delivers the tools. Your dataset stays in the browser.

The app files arrive first. Parsing, profiling, and cleanup then happen in a browser worker on your device. The dataset has no upload path.

  • No accounts
  • No cloud storage
  • No third-party scripts

Use the PII scan as an early warning—not as legal advice or a compliance certification.