EditorConfig Generator
Generate .editorconfig files online with indentation style, line endings, charset, and whitespace rules. Free and private.
Loading tool...
What is EditorConfig Generator?
An EditorConfig generator creates .editorconfig files that define consistent coding style rules for indentation, line endings, character encoding, and whitespace handling. Because the file lives in the project root, every editor and IDE that supports EditorConfig automatically applies the same rules to every developer on the team. This free tool builds a valid .editorconfig in seconds — no signup, no data leaving your browser.
Key Benefits
- Enforce identical indentation and style rules across every editor and OS
- Editors pick up the file automatically — no manual settings syncing
- Per-file-pattern rules for JavaScript, Python, YAML, Markdown, and more
- Stops endless tabs-vs-spaces and LF-vs-CRLF debates in code review
- One file in the repo root governs the whole project, including subdirectories
Common Use Cases
- •Onboarding new teammates with consistent formatting from day one
- •Ending tabs vs spaces and line-ending conflicts in mixed-OS teams
- •Standardizing style across a monorepo with per-language sections
- •Preparing open-source projects so contributors format code consistently
- •Pairing with Prettier or formatters for base-level editor defaults
How to Use the EditorConfig Generator
- Choose indentation and format rules: Pick indent style (space or tab), indent size, end-of-line (LF, CRLF, or CR), and charset. These apply to the files matched by your section pattern.
- Set whitespace options: Toggle trim_trailing_whitespace and insert_final_newline, and optionally set a max_line_length. Leave max line length empty to omit the property.
- Pick a section pattern: Use * to target all files, or a glob like *.js, *.{js,ts}, or lib/** to scope rules to specific file types or folders.
- Copy or download the file: Review the live preview, then copy the config to your clipboard or download it as .editorconfig and place it in your project root.
Key Features
- Full property support: indent_style, indent_size, tab_width, end_of_line, charset, trim_trailing_whitespace, insert_final_newline, and max_line_length
- Live preview that updates instantly as you toggle any setting
- Flexible section patterns such as *, *.js, or lib/** for per-file-type rules
- Root flag toggle to mark the topmost EditorConfig in your repository
- One-click copy or direct .editorconfig download, 100% in-browser
Frequently Asked Questions
What is an .editorconfig file?
It is a plain-text file that defines coding style rules — indentation, line endings, charset, and whitespace handling — that participating editors apply automatically. It lives in your repository, so every teammate gets the same settings without manual configuration.
Which editors support EditorConfig?
VS Code (via the built-in EditorConfig extension or plugin), JetBrains IDEs like IntelliJ and WebStorm, Sublime Text, Vim, Emacs, Notepad++, and Visual Studio all support it. Most pick up the file automatically once a plugin is installed.
What does root = true mean?
It marks the file as the topmost .editorconfig in the project. When an editor finds a file with root = true, it stops searching parent directories for more config files, which avoids accidentally inheriting rules from folders above your repository.
Can I use different rules for different file types?
Yes. EditorConfig files support multiple sections with glob patterns. For example, use [*] for defaults, [*.py] with indent_size = 4 for Python, and [*.{yml,yaml}] with indent_size = 2 for YAML. Later sections override earlier ones for matching files.