Can this recover the original source of a minified file?

No. Minification renames identifiers, removes comments, inlines functions and drops unreachable code — all irreversible. Beautifying restores indentation and line breaks so the structure is legible, but a, b and c do not become their original names again. Only a source map can do that.

Does formatting change how the code behaves?

The formatter is intended to preserve ordinary JavaScript behavior while changing layout. Unusual automatic-semicolon-insertion cases, unsupported syntax, or malformed input still deserve review. Test the result and use the original source map or repository formatter when behavior matters.

Why does my TypeScript or JSX come out wrong?

Because this formatter targets JavaScript, and neither type annotations nor JSX are part of that grammar. The parser encounters syntax it does not model and lays it out badly. Use Prettier, which understands both, for those files.

Should I use this to format my project's code?

No. Formatting a project needs a tool configured in the repository and run automatically, so every contributor produces identical output and diffs stay clean. Prettier or ESLint is the right answer there. This page is for code you are reading, not code you maintain.

Can I change indentation or other formatting rules?

No. This page applies two-space indentation with its built-in JavaScript beautifier settings. Use a configurable formatter in your project when you need tabs, another width, quote rules, trailing commas, or team-specific output.

Does beautifying execute or evaluate the JavaScript?

No. The text is passed to a formatter and displayed as text; the page does not run the program, import its modules, or contact referenced services. Formatting also does not prove the code is safe or syntactically valid.

JavaScript Beautifier and Formatter

Overview

Restore JavaScript structure without pretending to reverse minification

Run js-beautify's JavaScript formatter with a fixed two-space indent, then copy or download the readable result. Line breaks and indentation return; renamed identifiers, removed comments, bundled module boundaries, source filenames, and original intent do not.

JavaScript-specific formatting

The page targets JavaScript syntax rather than TypeScript, JSX, or a repository's full parser stack.

Two-space indentation

One fixed setting keeps the single-purpose interface predictable.

No un-minification claim

Short names, removed comments, and build transformations remain exactly as supplied.

beautified.js export

Copy or download the output for inspection without executing it.

How it works

Using JS Beautifier, start to finish

Three steps, in the order the tool above actually takes them.

1
Paste JavaScript text
Treat unknown code as untrusted and do not execute it merely because it becomes readable.
2
Inspect the beautified structure
Follow blocks, calls, literals, and control flow while remembering names may have been minified.
3
Use source maps when available
For your own build, map back to authored modules and names instead of relying on formatting alone.

Use cases

What people bring here

The jobs this page is usually opened for, and the setting that makes each one quick.

Reading a compact stack-trace snippet

Lay out copied JavaScript to make block and expression boundaries easier to follow.

Use the source map for exact source locations and original identifiers when the build supplies one.

Inspecting a third-party bundle

Create a readable view for security or integration review without executing the source.

Beautification does not establish safety, licence, provenance, or absence of dynamic behavior.

Explaining minification loss

Compare readable structure with permanently shortened names and removed comments.

The output can be easier to read while still being far from the authored source.

Formatting restores layout only

Beautification cannot reconstruct information removed by a build

Whitespace is recoverable because structure implies sensible layout. Identifier names, comments, module boundaries, dead code, and original file locations were discarded or transformed and require source maps or source access.

Artifact	Beautifier result	Better source
Indentation	The exact author's layout returns.	A consistent new two-space layout is generated from the current syntax.
Identifier names	a and b become descriptive variables again.	The formatter preserves the supplied names; only a source map may link them back.
Comments	Meaning can be inferred and comments regenerated.	Removed commentary is unavailable and should not be fabricated.
Behavior	Readable output is automatically safe to run.	Formatting neither executes nor audits the code; review unknown source as untrusted.

Indentation

The exact author's layout returns.

A consistent new two-space layout is generated from the current syntax.

Identifier names

a and b become descriptive variables again.

The formatter preserves the supplied names; only a source map may link them back.

Comments

Meaning can be inferred and comments regenerated.

Removed commentary is unavailable and should not be fabricated.

Behavior

Readable output is automatically safe to run.

Formatting neither executes nor audits the code; review unknown source as untrusted.

Privacy

Where your work is processed

JavaScript input is formatted as local text and never executed, uploaded, or autosaved.

Source content stays in the tab

Encoding, parsing, formatting, generation, comparison, and cryptographic operations run in browser code. Form values and uploaded text files are not sent to a processing API.

Inputs are not autosaved

Code, tokens, secrets, URLs, and generated outputs stay in component memory until the page reloads or closes. Split-pane tools remember only the divider percentage for the current tab session.

Clipboard and downloads are explicit

The page reads the clipboard only after a Paste action and writes it only after Copy. A local download is created only when you choose the tool's download control.

One aggregate page view may be counted

The page shell can send the tool slug, never the editor contents or filename. The endpoint is rate-limited using a transient requesting address and is skipped for Do Not Track or Global Privacy Control.

More detail in how processing works and our privacy policy.

Limits

Beautifier scope

The values this tool actually enforces, not a rounded-up version.

Language: JavaScript; TypeScript and JSX are outside the intended grammar.
Indent: 2 spaces; No configuration is exposed.
Execution: None; The input is formatted as text, never run.
Export: beautified.js; Copy and download use the current local output.

No source-map resolution, linting, deobfuscation, TypeScript, or JSX mode

JavaScript only — TypeScript annotations and JSX are outside the parser's grammar and may be formatted incorrectly. It formats; it does not lint, transpile, un-minify identifiers or resolve source maps. Indentation is fixed at two spaces with no configuration exposed on this page.

FAQ

JavaScript beautification questions

The ones that actually come up.

Developer tools

Choose a neighboring tool for the next step; each page states its processing and limits up front.

Base64 Encoder / DecoderRound-trip UTF-8 text through standard Base64, with invalid input reported clearly.Open URL Encoder / DecoderPercent-encode one URL component with encodeURIComponent, or decode it back.Open JSON FormatterA full JSON workspace for formatting, repair review, queries, conversion, and comparison.Open JSON Repair ProA repair review for malformed and AI-generated JSON, with a named rule behind every change.Open JSON to TypeScriptInfer TypeScript interfaces from one JSON example, with sampling limits stated.Open CSV to JSON ConverterA full data workspace for parsing, mapping, inspecting, cleaning, and converting tabular data.Open