⌘ K
prettier · babel · jsx · live

Format JSX with Prettier

Prettier's babel parser handles JSX elements, fragments, and embedded JS — wraps long attributes and indents children consistently. Runs locally.

JSX Formatter
Input
110 B
1 lines
Output
0 B
1 lines
Status
loading
parser…
Ratio
0.00×
out/in
input · jsx
output · formatted jsx
Loading parser…
Quick Start

How to format JSX

The babel parser reads JSX directly. Prettier wraps attribute lists, keeps fragments tidy, and indents children based on the width setting.

  1. 01

    Paste JSX source

    A component, a fragment, or an inline JSX expression — all flow through.

    Parsing runs through Prettier’s standalone bundle (or the language-specific equivalent) loaded lazily — no parser ships until the tool is opened.

    jsxPrettierASTstandalonelazy
    input · sourceraw · AST
    <div><Hi/></div>
    loaded · parsedAST · ready
  2. 02

    Pick style options

    Tab width, print width, semicolons, and single-quote behaviour are all configurable.

    Indent width, tab style, and print-width re-format through a memoised pass — switching 2 → 4 spaces never re-parses, only re-prints.

    optionsindentprint-widthmemoisedlive
    opts · optionsstyle · live
    semi=true
    options applied · livelive
  3. 03

    Live reformat

    Long attribute lists break, children indent, fragments stay readable.

    The formatter is deterministic and idempotent: running it twice produces byte-identical output, which keeps diffs and git noise to a minimum.

    liveidempotentdeterministicdiff-cleanstable
    out · formattedpretty · ready
    <div>
  <Hi />
</div>
    formatted · liveidempotent
  4. 04

    Copy or download

    Grab the .jsx file or copy to clipboard — input stays in the browser.

    Download writes a Blob with the language-appropriate extension; copy uses navigator.clipboard.writeText so the output preserves all whitespace exactly.

    exportclipboardbloblanguage MIMEclient-side
    ok · copiedready · done
    ✓ Copied
    shipped · ready to shipsuccess
Pro tips

Formatting tips that keep diffs sane

Pick one config and pin it

Inconsistent formatting causes diff churn. Commit .prettierrc / .editorconfig and enforce in CI.

Format on save

Editor integration is faster feedback than a pre-commit hook. Use both for belt-and-braces.

Idempotency matters

Running the formatter twice should produce identical output. Test this on a representative file.

Match the language community

Default to community conventions: 2 spaces for JS/CSS, 4 for Python, tabs for Go. Fights over indent are a productivity tax.

Print-width drives wrapping

80, 100, and 120 are the common targets. Wider lines parse fast but review slower side-by-side.

Don&rsquo;t mix formatters and linters

Prettier handles whitespace; ESLint handles correctness. Disable overlapping rules to avoid fight-club configs.

Related toolsTSX FormatterJS FormatterTS FormatterHTML FormatterMDX FormatterSort Imports
Use Cases

When to format JSX

Component snippets, sandbox code, doc embeds.

Component snippets

Tidy compressed JSX pasted from playgrounds. Idempotent: running the formatter twice produces byte-identical output, which is the foundation of a clean CI gate. Pair with a pre-commit hook so PRs arrive already formatted, focusing review on logic.

idempotent

AI output

Clean up JSX emitted by chat assistants. Pairs with EditorConfig + .prettierrc for end-to-end consistency. Whitespace-only changes vanish so reviewers see real diffs, and git blame stays honest about who wrote what.

CI-ready

Sandbox code

Make CodeSandbox / StackBlitz examples consistent. Output respects your indent width, tab style, and print-width — settings carry over for repeat runs. Switching 2-space to 4-space costs nothing in CPU but standardises an entire codebase.

diff-clean

Code review

Strip whitespace churn so diffs show real changes. Format-on-save is the fastest feedback loop; CI is the safety net. Together they make inconsistent indentation a thing of the past and free up review cycles for genuine concerns.

PR-friendly

Quick fix

Reformat without firing up your editor. Whitespace-only changes don't trigger downstream content-hash invalidations, so CDN cache keys and CI cache layers stay warm. Real changes get all the rebuild budget.

review-ready

Docs examples

Standardise JSX examples in component docs. Pairs with linters (ESLint, Stylelint, pylint) that catch what formatting alone can't — bugs, unused imports, dead code. Each tool stays in its lane, and the codebase stays clean.

deterministic
FAQ

Frequently asked questions

Both — the babel parser handles JSX, estree provides the AST shape Prettier expects.
For TSX use the TSX Formatter; this tool focuses on plain JSX.
Works fine — the babel parser accepts JSX in regular JS source.
No — use the Sort Imports tool for that.
No — Prettier runs locally in your browser tab.
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!