Oleg Brovchenko263 downloadsColor your Bases tags per-base. Each .base file owns its palette — no global tag soup.
Bring life to your tags. Per-base. No global mess.

Obsidian Bases has zero native pill colors. Bases Tag Colors fixes that — each .base file gets its own color palette stored in a sibling .colors.json. Colors follow the file. Nothing bleeds between bases.
.base file gets a sibling .colors.jsonmain.js, styles.css, manifest.json from the latest release.obsidian/plugins/bases-tag-colors/.base fileColors live in a sibling file next to your .base:
{
"version": 1,
"columns": {
"*": {
"B-Roll": "#78b7b8",
"VFX": "#9a5cb8"
},
"note.status": {
"Done": "#3a8c5c"
}
}
}
"*" — applies to any column in this base"note.status" — applies only in that specific column (wins over *)Save the file — colors update live, no restart needed.
| Command | What it does |
|---|---|
| Open color config for current base | Opens the .colors.json (creates skeleton if missing) |
| Seed config from current base values | Walks visible pills, pre-fills placeholder colors |
| Reload color config | Manual refresh without reopening the base |
| Migrate from colored-bases-properties | Copies your old colors into this base's own JSON |
Open your base → Settings → select it → click Import from active base.
The old plugin's data.json is read-only — nothing is modified.
Rollback: disable this plugin → all injected colors and DOM changes revert automatically.
![[Base.base]])Disable the plugin — all injected colors revert automatically.
Your .colors.json files remain in the vault (harmless). Delete manually if desired.
Made by Oleg Brovchenko