What does the .editorconfig Generator actually produce?

A plain-text .editorconfig file: a root = true line, a default [*] section with your indent, charset and newline choices, and any extra per-glob sections you add — ready to copy or download.

Which editors read the file this .editorconfig Generator creates?

Any editor with EditorConfig support, including VS Code (built-in since 2021), JetBrains IDEs (built-in), Vim, Sublime Text and Emacs with the EditorConfig plugin — the file format is a shared open standard.

Can the .editorconfig Generator set different indent rules per file type?

Yes. Add a glob like *.py or Makefile in the extra sections list and give it its own indent style and size — those override the default [*] section for matching files only.

Does the .editorconfig Generator upload my project settings anywhere?

No. Every option you choose stays in your browser tab; the file is assembled locally and only leaves your device when you copy or download it yourself.

What is the difference between indent_size and tab_width in an .editorconfig file?

indent_size controls how many spaces one indent level uses (or how wide a tab displays when indent_style is tab); tab_width is a separate, rarely-needed key for display width when it differs from indent_size.

Why does the .editorconfig Generator emit insert_final_newline = false instead of omitting the line?

When you explicitly turn a toggle off, the tool writes the literal false so the setting is enforced rather than left to each editor's own default — omitted keys are only left out when you never touched them.

.editorconfig Generator Online

Build a clean .editorconfig from indent, charset and newline options with per-language overrides, in your browser.

The .editorconfig Generator runs entirely in your browser. The indent, charset and section settings you choose never leave your device and nothing is uploaded to ArrayKit.

Open the .gitignore Generator

About .editorconfig Generator

The .editorconfig Generator builds a complete .editorconfig file from a handful of toggles so every editor on a team applies the same indent style, indent size, charset, line ending and trailing-whitespace rules. Start from a preset like 2-space/LF/UTF-8, tweak the default [*] section, then add per-language overrides for Makefiles, YAML, Python or any other glob that needs its own indent width or tab style. The generated output is a plain, copy-ready .editorconfig block plus a one-click download, so you can drop it straight into a repository root. It is built for developers and team leads who want consistent formatting across VS Code, JetBrains IDEs, Vim and every other editor with EditorConfig support, without arguing about tabs versus spaces in code review. Everything runs locally in your browser — nothing you configure is uploaded anywhere.

Features

Toggle indent style (spaces or tabs) and indent size for the default [*] section
Set charset, end-of-line style (LF, CRLF or CR) and trailing-whitespace trimming
Insert-final-newline toggle to keep files POSIX-friendly
One-click presets like '2-space, LF, UTF-8' to start from a sane default
Add extra [glob] sections for Makefile, *.md, *.py, *.yml and other file types
Each extra section gets its own indent style and size override
Copy-ready CodeBlock output plus a Download .editorconfig button
Runs entirely in your browser — no config is ever sent to a server

How to use the .editorconfig Generator

Pick a starting preset or leave the default [*] section as-is
Adjust indent style, indent size, charset, end of line and whitespace toggles
Add per-language sections for any glob that needs different indent rules
Copy the generated .editorconfig or download it straight into your repo root

Example

Input

2 spaces, LF, utf-8

Output

root = true

[*]
indent_style = space
indent_size = 2
charset = utf-8
end_of_line = lf
insert_final_newline = true

The default preset produces a minimal, portable .editorconfig section.

Common errors & troubleshooting

Editor still shows tabs even though the .editorconfig sets indent_style = space. — Confirm the file is named exactly .editorconfig, saved at the project root (or a parent folder), and that your editor has EditorConfig support enabled — most need a built-in setting or a small extension.
A Makefile section is being ignored. — Makefile targets require literal tabs by convention; check that the Makefile glob section in the .editorconfig Generator has indent_style set to tab, not space.
Settings from a later section aren't overriding an earlier one. — EditorConfig applies every matching section top to bottom, with later sections winning on conflicting keys — order your more specific globs after the default [*] section.
root = true doesn't seem to stop settings from a parent directory's .editorconfig. — root = true must be the very first line of the file, above any [section]; the .editorconfig Generator always places it there automatically.

Frequently asked questions

What does the .editorconfig Generator actually produce?: A plain-text .editorconfig file: a root = true line, a default [*] section with your indent, charset and newline choices, and any extra per-glob sections you add — ready to copy or download.
Which editors read the file this .editorconfig Generator creates?: Any editor with EditorConfig support, including VS Code (built-in since 2021), JetBrains IDEs (built-in), Vim, Sublime Text and Emacs with the EditorConfig plugin — the file format is a shared open standard.
Can the .editorconfig Generator set different indent rules per file type?: Yes. Add a glob like *.py or Makefile in the extra sections list and give it its own indent style and size — those override the default [*] section for matching files only.
Does the .editorconfig Generator upload my project settings anywhere?: No. Every option you choose stays in your browser tab; the file is assembled locally and only leaves your device when you copy or download it yourself.
What is the difference between indent_size and tab_width in an .editorconfig file?: indent_size controls how many spaces one indent level uses (or how wide a tab displays when indent_style is tab); tab_width is a separate, rarely-needed key for display width when it differs from indent_size.
Why does the .editorconfig Generator emit insert_final_newline = false instead of omitting the line?: When you explicitly turn a toggle off, the tool writes the literal false so the setting is enforced rather than left to each editor's own default — omitted keys are only left out when you never touched them.

Related tools

.gitignore Generator — Build a .gitignore from common language and tool templates.
robots.txt Generator — Visually build a robots.txt with user-agent rules, allow/disallow paths, crawl-delay and sitemaps.
Dockerfile Formatter — Format a Dockerfile and get best-practice / lint suggestions.
Nginx Config Generator — Build an nginx server block (static, reverse proxy, SSL, gzip, caching) from simple toggles.
.htaccess Generator — Toggle and configure common Apache .htaccess snippets with live output.
Meta Tag Generator — Generate SEO, Open Graph and Twitter Card meta tags for your page from a simple form.