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 →
EditorConfig is the closest thing the development world has to a peace treaty between text editors. The .editorconfig file lives at your project root and tells whichever editor a contributor is using — VS Code, IntelliJ, Vim, Sublime, Emacs — to apply the same indentation, charset, and line-ending rules. Stop arguing about tabs vs spaces. Stop fighting auto-format settings. Add an .editorconfig and everyone's editor agrees.
The syntax is INI-style. A `[*]` section applies to all files. `[*.{js,ts,jsx,tsx}]` applies to JavaScript/TypeScript only. Inside each section, the common keys are `indent_style` (tab or space), `indent_size`, `end_of_line` (lf, crlf), `charset` (utf-8), `trim_trailing_whitespace`, and `insert_final_newline`. Set `root = true` at the top of the file so editors know to stop walking up the directory tree looking for parent .editorconfig files.
IntelliJ products read .editorconfig natively. VS Code, Sublime, Atom, Vim, Emacs, and Notepad++ need a small plugin (free, install once and forget). The full spec lives at editorconfig.org. .editorconfig pairs well with formatters like Prettier, ESLint, or Black — EditorConfig handles the basic editor-level settings, and the formatter handles language-specific rules. Both reading the same source of truth keeps your codebase consistent without any one tool being the gatekeeper.
* Requires EditorConfig extension * Built-in support