Free EditorConfig test files and sample generator

The cross-editor coding-style config. Generate valid .editorconfig sample files to test editor tooling, linters and repo scaffolding.

Generate a .editorconfig file →

What is a .editorconfig file?

EDITORCONFIG: EditorConfig File. EditorConfig standardizes indentation and whitespace across editors. Its distinguishing feature is a preamble, `root = true` appears before any section, which strict INI parsers reject even though it is required by the spec.

Why generate a test EditorConfig file?

• Test an EditorConfig implementation, including the preamble before the first section.
• Verify glob-section precedence for multiple file types.
• Check repository scaffolding output.

How a .editorconfig file is identified

A .editorconfig file has no signature at the start. A text format has no identifying leading bytes, so the extension and the reported media type are the only claims about it until a parser actually reads it, which is why validating uploads by extension alone is unsafe.

How the size lands on the exact byte

The format allows comments, so the padding is comment lines, legal, inert, and visible if you open the file.

Negative testing with broken EditorConfig files

• Invalid. Identifiable, but wrong inside, so it fails during parsing.
• Corrupted. The leading bytes are destroyed. Same length as the valid file.
• Incomplete. Truncated part-way, so it is genuinely shorter.
• Empty. Chosen under Content rather than File Condition: valid structure, no data.

Which failure to reach for, and what to assert for each, is covered in how to make a corrupted file for testing. For upload limits and type checks see testing file upload validation, and for this format's encodings, UTF-16 and BOM test files.

Sample EditorConfig content

root = true

[*]
indent_style = space
indent_size = 2

This shows the shape of the file. Your download is generated fresh at the size you choose, so the values will differ.

How to open and verify the file

Any text editor; validate with the `editorconfig` CLI or your editor's plugin.

Media type text/plain · extension .editorconfig · category Config & DevOps

Generate a .editorconfig file → · questions about sizes, privacy or cost are answered on the site FAQ.

Frequently asked questions about EditorConfig files

What identifies a .editorconfig file?

Nothing at the start of the file does. A text format has no identifying leading bytes, so the extension and the reported media type are the only claims about it until a parser actually reads it, which is why validating uploads by extension alone is unsafe.

How can a .editorconfig file be an exact number of bytes?

The format allows comments, so the padding is comment lines, legal, inert, and visible if you open the file.

Can I download several broken EditorConfig files at once?

Yes, select more than one File Condition and you get one ZIP containing a .editorconfig per condition, each named after its condition.

Can the EditorConfig file use UTF-16 or a byte-order mark?

Yes. .editorconfig is a text format, so it can be generated as UTF-8, UTF-8 with a byte-order mark, UTF-16 LE or UTF-16 BE. The body is shortened before re-encoding so the finished file still lands on the exact size you asked for. Note that a UTF-16 file always has an even byte count.

How do I open or verify the EditorConfig file?

Any text editor; validate with the editorconfig CLI or your editor's plugin.

Related Config & DevOps formats

ENV · INI · TOML · Dockerfile · gitignore · CONF · Properties · Makefile

Browse all file formats →