Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Live File ColorsNew to Visual Studio Code? Get it now.
Live File Colors

Live File Colors

Toximiner

| (0) | Free
PyCharm-style file name colors for unsaved changes in editor tabs and Explorer.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Live File Colors

Color tracked file names as soon as you edit them, before saving — in editor tabs and Explorer.

This extension adds the missing unsaved state to VS Code's native Git decorations. Tracked files without an existing Git status become blue while their document has unsaved changes. Existing statuses for added, untracked, renamed, modified, ignored and conflicted files remain managed by VS Code's Git extension.

Try locally

Install the VSIX, open a Git repository and edit a tracked, unchanged text file. Its name turns blue without saving. Restore the original text, either by Undo or by editing it back manually, and the overlay disappears even if VS Code still marks the document as unsaved. After saving, native Git colors apply.

If Auto Save is enabled, the unsaved state lasts until the next automatic save.

Settings

  • liveFileColors.enabled: enable or disable the overlay (default: true).
  • workbench.colorCustomizations → liveFileColors.unsavedForeground: customize the unsaved name color.
{
  "workbench.editor.decorations.colors": true,
  "explorer.decorations.colors": true,
  "workbench.colorCustomizations": {
    "liveFileColors.unsavedForeground": "#6897BB",
    "gitDecoration.modifiedResourceForeground": "#6897BB",
    "gitDecoration.stageModifiedResourceForeground": "#6897BB"
  }
}

VS Code problem decorations may take precedence over file colors. To prefer Git/unsaved colors on file names, set problems.decorations.enabled to false. This does not disable diagnostics in the code or the Problems panel.

Scope and privacy

Uses the public File Decoration and built-in Git APIs. Supports tracked file-backed text documents in Git repositories. Untitled, ignored, untracked and virtual documents receive no extra overlay. Parent folders inherit the unsaved decoration. The extension never saves, stages, commits, changes Git configuration or edits VS Code files. It has no telemetry or network requests. The extension reads the HEAD document through VS Code’s built-in Git provider and caches its text until the repository changes. It compares that text with the current buffer, without saving. CRLF and LF line endings are treated as equivalent.

The live comparison applies to files without an existing Git status. For a file already marked modified by Git, the native Git decoration remains authoritative until the file is saved and Git refreshes.

Development

npm ci
npm run check
npm test
npm run package

MIT license.

Installation

Install Live File Colors by Toximiner from the VS Code Extensions view, or run:

code --install-extension Toximiner.live-file-colors

Visual Studio Marketplace · GitHub releases and VSIX downloads

If installing a downloaded VSIX, use Extensions: Install from VSIX…. Reload VS Code if a newly installed extension has not activated yet.

Releases

GitHub Actions validates and packages every main-branch change and pull request. A matching version tag, such as v0.1.0, creates a GitHub release with the VSIX and SHA256 checksums, and publishes to the Marketplace through Trusted Publishing. No publisher token is stored in this repository.

The host integration test in tests/host.cjs can be run using VS Code's --extensionTestsPath against a disposable Git repository containing a committed example.py. It edits and saves that fixture; do not point it at a working repository.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft