Bases Toolbox

Quality-of-life tools for Bases and properties in Obsidian.

Features

Find & replace property values

Command: Find & replace property values. Pick a property, then either replace one specific value everywhere it appears or override every value at once. Works on list properties too (the matched item is replaced in place; a global override collapses the list to the new value). Leaving the replacement empty clears the value.

Every run is logged. Find & replace history opens as a main-area tab listing all past operations (newest first, uncapped by default — an optional cap and a clear-history action live in the settings). Each entry expands into per-file rows showing old → new with an "edited since" badge on drifted files; revert all of an operation or just the files you check. Undo last find & replace reverts the newest active entry. Reverts are best-effort: files whose value was edited again are skipped and reported — unless you enable the force toggle, which overwrites them. An entry only counts as reverted once nothing from it remains in effect, so you can always retry. The log survives app restarts.

Number input guard

Number properties — in the frontmatter editor and inside Bases views — no longer change value when you press ArrowUp/ArrowDown or scroll the mouse wheel over a focused input. Optionally, only digits, . and - are accepted as typed characters (so no stray e exponents). Both behaviors are toggles in the plugin settings and are on by default.

Bulk edit base results

Command: Bulk edit properties of base results. With a base open, act on every file the view currently shows — filters, search, everything applied. Five modes: set (replace), set only if missing (backfill defaults without clobbering), append / remove list items, and delete the property entirely. All logged in history and revertible; reverting a bulk-create deletes the property again, reverting a delete restores it.

Rollups into real properties

Command: Compute rollup into property. For every result of the open base, count/sum/average/min/max over the notes linking to it (or linked from it) and write the result into a real frontmatter property that Bases can display and sort natively. One-shot — re-run to refresh. Logged in history, revertible.

Conditional formatting

Color Bases rows — or individual cells — by rules, on all bases or a chosen subset of them (a per-rule sheet picker). Each rule has a property, operator (equals/contains/compare/empty), value, a scope (color the whole Row or just that property's Cell), and a color from the theme palette or a custom color picker (applied at a subtle tint). Rules are fully editable inline, reorderable (they apply top-to-bottom; first match wins per row and per cell), and each shows a color swatch. Changes apply to open bases in real time. Managed in the plugin settings or a dedicated sidebar panel (command: Open conditional formatting panel) that pops out to a main tab.

CSV import & export

Both Import CSV as notes and Export to CSV are their own panels — open either from the launcher, and like every panel it can live in the sidebar, its own tab, or a separate window. Each also has a dialog.

Import CSV as notes: paste or pick a CSV/TSV → per-column property name, type (text/number/date/boolean/list/link), include toggle, filename column → one note per row in a target folder, with an optional auto-created .base. Dates are normalized (US, European, month names, Excel serials); quoted fields may contain newlines.

Export to CSV — the panel / dialog has two tabs:

• From a base: pick any .base file (no need to open it) and load it — you see its base-level filters, choose which view to export (bases can have several, each with its own filters and columns), and see that view's filters and column order before exporting. It resolves the built-in file.* columns (name, path, folder, ext, size, ctime, mtime, tags) plus your frontmatter properties. Formula columns and link-lists (which need Bases' live engine) come out blank, and a view with filters beyond folder scope is flagged as a best-effort superset. A "Write readable summary (.md)" button emits a plain-language note of the base's filters, formulas, sort, and grouping — the things a flat CSV can't hold — so you can rebuild them in your spreadsheet. The exporter lists these limitations inline.
• From a folder: pick any folder and load it — check off any subfolders to ignore, and see the non-markdown files a CSV export skips (images, PDFs…). One button companions them (creates queryable notes) regardless of your companion settings, so they're included on the next load. Then every note's frontmatter becomes a CSV row, with a column per key found.

Both preview first, with a column checklist (all on by default) so you pick what to include, then "Copy for Excel" (TSV to clipboard) or write a .csv (next to the base, or in the folder). Wikilinks are unwrapped and lists joined with ";". Output is multiple files (CSV + optional summary), not a zip.

For a base's exact live filtered results with formula columns evaluated, open the base and run the "Export active base results as CSV" command — it uses Obsidian's live query engine and errors on any non-base view.

Merge notes & duplicate finder

Merge current note into another: frontmatter-aware — properties missing on the target are copied, list properties union, and scalar conflicts get a per-property picker. The source's body is appended, links to the source are re-pointed at the target (aliases preserved), and the source moves to the vault trash (recoverable). No automated undo — check the plan in the modal before confirming.

Find duplicate notes: group candidates by similar file names (case, punctuation, and "copy"/number suffixes ignored), by equal values of a property you choose, and/or by identical bodies. Pick the note to keep per group and merge the rest into it.

Filter quick-toggle

Command: Toggle base filters. Disable individual filter conditions of a .base without deleting them — disabled filters are remembered by the plugin and can be re-enabled later. (Nested filter groups are listed but not yet toggleable.)

Cell zoom editor

Command: Zoom into focused cell. Click into a Bases cell or a property value in the frontmatter panel, run the command (bind a hotkey), and edit the value in a proper multi-line editor. List properties edit one-item-per-line. Saved through Obsidian's frontmatter API.

Embedded-base display options

Control how an embedded base renders via flags in the embed's alt text:

![[My Base.base|bases-no-toolbar]]        hide the toolbar row
![[My Base.base|bases-no-header]]         hide the whole header
![[My Base.base|bt-height-300]]           fix the embed height (px)
![[My Base.base|bases-no-header bt-height-150]]   combine them

No CSS snippets needed; flags apply per embed.

Multiline list cells

Settings toggle: list-property values in Bases table cells stack one per line instead of a single row of pills. Rows in Bases are fixed-height (virtualized), so long lists scroll inside the cell — pair with the Bases row-height option for taller rows.

Property index

Command: Open property index (also a ribbon icon). A sidebar view listing every frontmatter property in the vault with its type, file count, and — when expanded — every distinct value with usage counts. Built straight from the metadata cache, so it never forgets a property the way the Bases filter menu can. Each property and value has a shortcut into find & replace.

Bases built-in properties (and Obsidian's forgetful picker)

Obsidian's Bases property menu sometimes drops the built-in file.* attributes, so a column you want — created time, tags, folder — isn't offered. They aren't formulas; you can re-add any of them by its identifier:

Identifier	What it is
file.name	note name (no extension)
file.ext	file extension
file.path / file.folder	full path / containing folder
file.size	size in bytes
file.ctime / file.mtime	created / modified time
file.tags	every tag (frontmatter + body)
file.links / file.backlinks / file.embeds	outgoing links / backlinks / embeds
file.properties	all frontmatter properties on the file

To add one: in a table view open a column's property menu and pick it under File — or edit the .base file directly and add the identifier to a view's order: list:

views:
  - type: table
    order:
      - file.name
      - file.ctime      # re-added built-in
      - file.tags

For a formatted or computed column (a readable date, a derived value), use a formula instead — add a formulas: block and reference it as formula.<name>:

formulas:
  created: file.ctime
views:
  - type: table
    order:
      - file.name
      - formula.created

…then rename that column's header in the view. Obsidian 1.9.5+ ships a built-in formula editor (autocomplete + docs), and the community plugin Formula Forge adds global formulas and renders them inline — reach for either if you're writing anything beyond a bare file.* reference.

This "forgetting" is Obsidian's behavior, not something this plugin can patch — but the property index above never forgets your properties.

Recipe: look up a value from a linked note (a Bases "XLOOKUP")

Bases has no built-in relational lookup, but if a property links to another note, a formula can pull one of that note's properties in — the equivalent of Excel's XLOOKUP. Say each Transaction links to an Account (account: [[Chase 1234]]) and you want the Account's bank name as a column:

formulas:
  bank: account.asFile().properties.bank

For property names with spaces or symbols, use bracket syntax on both sides:

formulas:
  holder: note["Account"].asFile().properties["Account Holder Name"]

Then add formula.bank / formula.holder to the view's order. It's the relational join Bases doesn't give you out of the box. (This is a plain Bases formula recipe, not a plugin feature.)

Property format doctor

Command: Property format doctor. Obsidian flags type-mismatched property values but "corrects" them destructively — sometimes erasing the value outright. The doctor opens a tab listing every value in the vault that doesn't match its property's assigned type (number, checkbox, date, datetime, text, list, tags, aliases), explains what each type expects with an example, and pre-fills a suggested fix only when one is safe (dates get normalized, yes becomes true, scalars become one-item lists, a date in a datetime slot gains T00:00). Everything is editable before applying; inputs that still don't match are marked red and the file is left untouched; an empty input means "skip" — a value is never erased. Applied fixes are logged to history and revertible.

Convert or fork a property's format

Command: Convert or fork a property's format. For frontmatter that predates Bases — dates like 3/4/2024 or February 3 2025, or values wrapped in [[wikilinks]] where you want raw text (or vice versa). Pick a property and a transform (normalize dates → YYYY-MM-DD, unwrap wikilinks, wrap in wikilinks, plain copy), preview the effect, then either convert in place or fork into a second property so you keep your original format AND a Bases-friendly variant side by side. Forks can be kept in live sync — edit the original and the fork recomputes automatically. Live syncs are managed in the plugin settings: pause one without deleting it, delete it (deleted syncs move to a restorable "recently removed" list), or open the fork builder to add another. Every apply is history-logged and revertible.

Allowed values (pinned)

From the property index, pin the allowed values of any property (pin icon). Editing a pinned property — in the frontmatter panel or a Bases cell — shows a picker of the allowed values, and the Audit allowed values command lists every value that falls outside a pinned list, with one-click jumps into find & replace.

Companion notes for non-Markdown files

Command: Create companion notes for non-Markdown files. Bases only reads frontmatter from .md files — images, PDFs, audio, and other attachments are invisible to it. This scans a folder (or the vault), optionally filtered by extension, and creates one companion note per file (named <file>.<ext>.md) whose frontmatter replicates the file's metadata — file-name, file-ext, file-size, file-created, file-modified, file-path — plus a companion-of link and an embed of the file in the body. Companions live adjacent to their files by default, or collected into a designated folder mirroring the source structure. Re-running refreshes the file-* properties while preserving anything you added to a companion; originals are never touched, and files derived from notes (like version files other plugins create) are never companioned. Every non-Markdown file is eligible by default; settings let you exclude specific extensions (managed as chips, with every file type found in your vault listed so you can click to exclude it), set a default destination, and turn on an opt-in auto mode that companions files as they're added — enabling it also companions eligible files that already existed.

Stamp file metadata into note properties

Command: Stamp file metadata into note properties. Filesystem created/modified times get destroyed by syncs, copies, and migrations — frontmatter travels with the note forever. This snapshots each Markdown note's current times into properties of your choosing (default created / modified), scoped to a folder or the vault. Set-if-missing by default, so existing values are respected; overwrite is opt-in. Logged to history and revertible.

Inline-field migration

Command: Migrate inline fields to properties. Scans for Dataview-style Key:: value lines (and optionally [key:: value] spans), previews what it found, and writes them into frontmatter so Bases can query them. Optionally cleans the migrated fields out of note bodies (off by default — that part isn't revertible; the frontmatter side is, via history). Scope to a folder or the whole vault; existing properties are skipped unless you opt into overwriting.

Tips & recipes

Fork any note (duplicate + rename in one go): Obsidian's core Templates plugin already covers new-note-from-template, so this plugin doesn't ship a templates feature. To quickly clone an existing note and rename it, install the community Commander plugin and bind a macro that runs Create new note and then Rename file back to back — one click forks the note you're on.

Writing formulas: for anything past a bare file.* reference (see Bases built-in properties above), use Obsidian 1.9.5+'s built-in formula editor, or Formula Forge for global formulas and inline rendering. A full formula builder is out of scope here — those tools do it well.

Credits & related plugins

Parts of this plugin overlap with — and were inspired by — existing community work. Credit where due, and if one of these fits your workflow better, use it. What each is capable of:

• Mass Editor (MIT) — shipped while this plugin's find & replace was already in development (built independently). Reviewing its code later inspired several history refinements here — selective per-file revert, the force-revert option, and set-if-missing/delete bulk modes — as concepts; no code was copied, our implementations are our own. Capabilities:
  • query builder over tags, frontmatter, and body text
  • bulk frontmatter set / add / delete / append on the matched notes
  • automatic per-run backups with a history panel
  • selective undo with drift detection and git-style diffs
• Better Properties — the full-featured take on property editing (BRAT install):
  • select-style fields with predefined value lists per property
  • extra property input types beyond core's set
  • rename or delete a property across the whole vault from the property menu
• Metadata Menu — the heavyweight metadata suite (requires Dataview):
  • fileClass schemas: define which fields a kind of note has
  • select / multi-select fields with predefined and dynamic values
  • lookup fields that aggregate over Dataview queries and persist results into frontmatter (count / sum / average / custom JS)
  • edit any field from context menus, links, or buttons anywhere in the app
• Multi Properties — bulk property editing:
  • add or overwrite properties on many notes at once
  • works on folders, multi-selected files, and search results (this plugin covers the missing scope: the live results of a Bases view)
• Dataview to Properties — converts Dataview inline key:: value fields into frontmatter properties (our migrator adds folder scoping, a dry-run preview, and revertible writes)
• Bases Lock — per-embed control of embedded bases:
  • hide the toolbar / lock header interaction with |x / |o embed flags (reading view; our flags add a fixed-height option)
• Colored Bases Properties — automatic, hash-based colors for property value pills in Bases views (our conditional formatting instead colors whole rows by explicit rules)
• Dualyze Notes — finds similar notes by weighted title / heading / tag / link / body similarity and builds side-by-side merge drafts for their bodies
• Merge Notes — straightforward concatenation of two notes into one (our merge adds frontmatter awareness: list union + per-conflict picker)
• CSV-to-Obsidian-Properties-for-Bases — the companion browser tool our CSV import's converter core is ported from (same author as this plugin):
  • paste/drop CSV or TSV, map columns to typed properties, live preview
  • downloads a ZIP of ready-to-drop .md files — no install, works offline

Permissions & data

Bases Toolbox runs entirely on your machine. It has no network access — it never sends anything anywhere, and there is no telemetry or analytics.

• Reading the list of files in your vault — the property index, vault-wide find & replace, companion-notes scan, base discovery, and merge all need to enumerate file paths (vault.getFiles / getMarkdownFiles). This stays local; it's what lets the plugin offer "a searchable index of every property" and replace a value everywhere it appears.
• Clipboard — used write-only. When you click a Copy button (copy property name, copy value, copy file path, or copy a CSV export) the plugin writes to the clipboard. It never reads the clipboard, so nothing you've copied from elsewhere is ever accessed.
• Reading and writing note files — property edits, find & replace, and the format doctor modify frontmatter through the standard Obsidian file API, only when you ask them to.

Development

pnpm install
pnpm run dev        # watch build
pnpm run build      # production build
pnpm run deploy     # build + copy artifacts to the vault(s) in .deploy-target

.deploy-target (gitignored) holds one <vault>/.obsidian/plugins/bases-toolbox path per line.