Home › Formats › .EditorConfigID
What is a .EditorConfig file?
An .editorconfig file sets consistent coding styles across different editors and IDEs.
- Did you know
- EditorConfig, adopted around 2012, lets a whole team’s editors agree on indentation and spacing.
- EditorConfig was proposed in 2012 by Trey Hunner and consists of the file format plus a collection of editor plugins.
- Its sections are filepath globs in an INI-style syntax, so one file can apply different rules to different parts of a project.
- What Analyser reads
- Identify and read metadata from developer and data files: JWT tokens (header + claims + expiry), WebAssembly, Java class files, NumPy/Safetensors/GGUF model files, source maps, SQL dumps, Visual Studio/.NET projects, Terraform, Protobuf, GraphQL, SARIF, Python bytecode, and Apple property lists (XML + binary). Jupyter notebooks (IPYNB) and HAR captures now open in a full viewer - see Notebooks & data above.
- Depth of analysis
- .EditorConfig is an identification-grade format: Analyser recognises it from its bytes and decodes the header metadata it carries, rather than opening it in a full viewer. Formats that do get a full viewer are marked "Full" on the formats page.
- Open a .EditorConfig file
- Drag a .EditorConfig file onto the Analyser home page (or tap to pick one). It is identified entirely in your browser - nothing is uploaded, there is no account, and it works offline once installed.