Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
Prettier is an opinionated code formatter — feed it source code, it gives you formatted source code with no debate about style. The .prettierrc file is its config: a small JSON or YAML object setting maybe a dozen knobs (`tabWidth`, `singleQuote`, `printWidth`, `trailingComma`, `semi`). Prettier deliberately resists adding more — the appeal is exactly that there's nothing to argue about beyond the few essentials.
Format variants — .prettierrc, .prettierrc.json, .prettierrc.js, .prettierrc.yaml, .prettierrc.toml. Prettier auto-detects which based on the contents. The bare .prettierrc holds JSON or YAML; the auto-detection occasionally surprises people, so most teams pick an explicit extension for clarity. A typical .prettierrc.json is five lines: tab width, semicolons, single quotes, trailing comma, print width.
Prettier pairs with ESLint via `eslint-config-prettier` — a config that disables every ESLint rule that conflicts with Prettier's formatting. The division of labour is clean: Prettier handles formatting (whitespace, line breaks, quote style), ESLint handles code quality (unused variables, undefined references, accessibility issues). CI integration is `prettier --check .`, and editor integrations format on save in VS Code, IntelliJ, Vim, Emacs, and pretty much everything else.
* Prettier extension provides format-on-save