Hex Preview

A small Obsidian plugin that adds inline swatches to #RRGGBB and #RRGGBBAA colors.

Features

• Case-insensitive six- and eight-digit hex detection. No shorthand, RGB, or HSL syntax.
• Live Preview and Reading view: swatches beside colors in prose and inline code.
• Native Bases tables, including embedded Bases: previews in text properties, individual list-property pills, and rendered formula values when the entire value is a hex color.
• Checkerboard backgrounds make transparency visible. The final two digits specify alpha (00 transparent, FF opaque).
• Click a swatch to open a hue ring with an inner saturation/value square, RGB and Hexa inputs, and an opacity control. Select Apply to update that occurrence; the × close button, Escape, or an outside click leaves the original value untouched.
• Native Bases text, property controls, sorting, and filtering remain intact. Swatches disappear in focused text editors.
• Previewing never changes notes. Applying a color updates the selected hex value or Bases property entry. No network requests, settings, or custom view types.

Install from GitHub

1. Download main.js, manifest.json, and styles.css from the latest release.
2. Place all three files in <vault>/.obsidian/plugins/hex-preview/, replacing previous plugin files when updating.
3. Restart Obsidian and enable Hex Preview under Settings → Community plugins.

Install the local build

1. Copy the dist/hex-preview folder into <vault>/.obsidian/plugins/.
2. Reload Obsidian.
3. In Settings → Community plugins, enable Hex Preview (plugin ID: hex-preview).

The folder contains main.js, manifest.json, and styles.css. For development, these files are also available at the project root after building. Do not install the entire source tree or node_modules into your vault.

Usage

Write #23264F or #23264F80 in a note, optionally in inline code. A small swatch appears before the original text. Bare hex values can still be Obsidian tags; the plugin preserves that behavior. Inline code avoids the ambiguity.

Click or keyboard-focus the swatch and press Enter/Space to open the picker. Drag on the hue ring to select a hue, then use the inner square to adjust saturation horizontally and brightness vertically. Arrow keys adjust hue on the ring; in the square, left/right adjust saturation and up/down adjust brightness. Hold Shift for larger steps. Enter RGB channel values from 0 to 255 or a six/eight-digit Hexa value (with an optional #); both input rows update the ring and square immediately when valid. The opacity slider previews the selected color over a checkerboard, with an editable 0–100% value on its right. Changing opacity fades both the hue ring and the inner square over a checkerboard while keeping their selection markers visible. Six-digit Hexa input preserves opacity; eight-digit input sets it explicitly. Incomplete or invalid inputs cannot be applied. Opacity preserves the original alpha unless changed; lowering it on a six-digit color produces an eight-digit value. Existing eight-digit values stay eight digits, even at full opacity. Apply saves once, and Live Preview edits can be undone normally.

Reading view edits are limited to colors that can be mapped unambiguously to the source section. If that mapping is unavailable, the picker explains that you need to use Live Preview. If the source changes while the picker is open, applying is refused until you reopen it.

For Bases, store a hex color in a text property or each entry of a list property. When editing YAML directly, quote values beginning with #:

---
color: "#23264F"
colors:
  - "#23264F"
  - "#23264F80"
---

Add color or colors as a column in the existing table view. No changes to the .base configuration are required. The examples/ folder contains two sample notes and a Base; copy the folder to Hex Preview examples in a test vault to try both note and column previews.

Keep File name visible when editing colors in Bases so the picker can identify the note behind each row. Only the clicked list entry is changed, including when the same color occurs multiple times. Calculated/formula values can be explored in the picker but cannot be written back. Bases edits use Obsidian's frontmatter API, which may normalize YAML formatting.

Deliberate boundaries

• Source mode, fenced code blocks, link destinations, linked filenames, frontmatter source, and math are excluded from note previews.
• Bases previews require a whole text value or list item to be a valid hex color. Arbitrary prose inside a property cell is not decorated.
• Ordinary Properties panels outside Bases are not included.
• Hex-looking tags keep their existing tag behavior.
• Bases integration relies on native .bases-table-cell markup because there is no documented cell-decoration hook. It may need adjustments after Obsidian updates.
• Minimum declared version: Obsidian 1.10.0. Local development uses API types from 1.14.4. Mobile and pop-out window behavior still need manual verification.

Development

Use Node.js 24 and pnpm 11.25.0, matching the release workflow.

pnpm install
pnpm lint
pnpm test
pnpm build

pnpm dev watches source changes and rebuilds main.js. pnpm build type-checks and produces the installable folder in dist/. CodeMirror and Obsidian are provided by the host app and excluded from the bundle.

pnpm lint enforces the Obsidian DOM-helper rule and the TypeScript/JavaScript rules reported by the community review. The release workflow runs these checks before testing and building.

The tests cover matching boundaries, editor syntax exclusions, preservation of native Bases nodes/text, list values, focus behavior, recycled cells, dynamic rows, cleanup, RGB conversions, alpha preservation, picker interactions, duplicate occurrences, and protection against stale edits.

Inspired by obsidian-color-preview. This is a new implementation focused on hex previews.

Releases and provenance

Update manifest.json, package.json, and versions.json, commit the changes, and push a matching x.y.z tag. The Release workflow installs locked dependencies, runs lint checks and tests, builds the plugin, generates GitHub artifact attestations, and publishes only the three files used by Obsidian: main.js, manifest.json, and styles.css. The MIT license remains in this repository.

Dependency installation and build commands run in a job with read-only repository access and no signing permissions. A separate job on a fresh runner downloads the exact artifact ID produced by that workflow run, rejects digest mismatches, and validates the three release files before signing and publishing them. This privileged job does not check out repository code, install dependencies, or execute the downloaded plugin. Actions are pinned to full commit hashes. This isolates publishing credentials from build dependencies; attestations prove provenance, not that the plugin or its dependencies are vulnerability-free.

For an existing release, run the workflow manually with its tag from a ref containing the same build inputs. It rebuilds the plugin and compares all three files byte for byte with the published assets before attesting them. It refuses mismatches and never overwrites an existing asset.

After downloading a release asset, verify its build provenance with the GitHub CLI:

gh attestation verify main.js --repo PaulRenvoise/obsidian-hex-preview
gh attestation verify styles.css --repo PaulRenvoise/obsidian-hex-preview