Skip to content
ToolQivo

EditorConfig Generator

Make every editor agree on indentation, line endings and charset.

Developer Tools Reviews Free · no sign-up
Per-language overrides

Quick Tool Overview

The EditorConfig Generator states a project’s formatting rules once so every editor obeys them, with the per-language overrides that are not optional — tabs for Make and Go, no trailing-whitespace trimming in Markdown, CRLF for batch files.

What it does
Generates an .editorconfig file
You give it
Your indentation, line endings and languages
You get back
A file every editor understands
Best for
A team where people use different editors
Developer Tools Free, unlimited use No sign-up Runs in your browser

About the EditorConfig Generator

An .editorconfig file is how a project states its formatting rules once and has every editor obey them, whether the person opening it uses VS Code, a JetBrains IDE, Vim or something else. Most editors support it natively; the rest have a plugin.

The per-language overrides are the part worth getting right, because a few languages will simply not tolerate the global default. Make requires real tabs and fails with a cryptic error on spaces. YAML forbids tabs outright. Markdown uses two trailing spaces as a line break, so trimming trailing whitespace silently rewrites the document. Go is formatted by gofmt, which uses tabs and will not be argued with. Each override here carries a comment saying which of those it is there for, so nobody deletes it six months later.

Key features of the EditorConfig Generator

The overrides that are mandatory

Make needs real tabs, YAML forbids them, and Markdown treats two trailing spaces as a line break. Each one is a rule you cannot set globally.

Every override explained

A comment on each block saying which language quirk it exists for, so nobody deletes it six months later as untidy.

root = true included

Which stops the search walking up into a stray file in someone’s home directory and quietly changing the rules.

Tabs handled correctly

Choose tabs and it writes tab_width rather than indent_size, which is the field that actually applies.

Works everywhere

Most editors read .editorconfig natively; VS Code and the JetBrains IDEs need one small plugin.

How to use the EditorConfig Generator

  1. 1

    Set the defaults

    Indent style and size, line endings, charset and whether to trim trailing whitespace.

  2. 2

    Add language overrides

    Markdown, Makefile, YAML, Python, Go, PHP, JSON, batch files and patches.

  3. 3

    Save to your repository root

    Name it .editorconfig — root = true stops the search going any higher.

  4. 4

    Check your editor

    VS Code and JetBrains IDEs need a plugin; most others read it out of the box.

Frequently asked questions

No — they cover different moments. EditorConfig tells your editor how to behave as you type; a formatter rewrites the file on save or in CI. They overlap on indentation, so set the same values in both or the two will fight.

Reviews of the EditorConfig Generator

What people who use the EditorConfig Generator think of it. Reviews come from visitors and are posted as written.

No ratings yet

Yours would be the first.

  • 5 0 reviews rated 5 stars
  • 4 0 reviews rated 4 stars
  • 3 0 reviews rated 3 stars
  • 2 0 reviews rated 2 stars
  • 1 0 reviews rated 1 star

Write a review

Used this tool? Your rating helps the next person decide.

Your rating

Plain text only — links, email addresses and HTML are not accepted. Your name and review are shown publicly; nothing else is collected. See the privacy policy.

0 reviews

Newest first

No reviews yet

Be the first to rate the EditorConfig Generator. It takes half a minute and no account.

Write the first review

More developer tools