.editorconfig Generator
Generate a .editorconfig file with indent_style, charset, end_of_line and trim_trailing_whitespace. Standardizes editors across teams. Everything in your browser.
One indentation for the whole team
One dev uses tabs, another uses two spaces, a third saves with CRLF, and the pull request shows up with 400 changed lines and zero logic touched. .editorconfig deals with that at the source: everyone's editor starts following the same indent_style, indent_size, end_of_line and charset. Tick the options here and copy the finished file, which already opens with root = true and a [*] section.
A detail almost nobody mentions: VS Code does not read .editorconfig on its own, it needs the EditorConfig for VS Code extension. JetBrains IDEs and Visual Studio support it natively, while Vim and Sublime want a plugin. And root = true means stop looking in parent folders. In a monorepo only the file at the top should carry that line, otherwise a package further down quietly ignores the shared rules.
The output has a single [*] section covering every file. In practice you add exceptions by hand: [*.md] with trim_trailing_whitespace = false, because two trailing spaces are a line break in Markdown, and [Makefile] with indent_style = tab, because make rejects spaces. Skip utf-8-bom unless some Windows tool insists, since a BOM breaks shell scripts. The file is assembled in your browser.
Frequently asked questions
Does .editorconfig replace Prettier?
Where do I save the file?
Will it fix files that already exist?
Related Tools
VS Code Snippet Generator
Build a JSON snippet ready to paste into VS Code *.code-snippets files, with prefix, multi-line body and tabstops $1, $2.
Cron Expression Editor
Parse and build cron expressions with human-readable descriptions, next execution times and shortcuts for common schedules.
Express Route Pattern Tester
Tests a URL against Express-style route patterns (/users/:id), showing which one matches first, the extracted params and route conflicts.