Vault Reader

approved

by MaverickHQ

Focused speed reading for Obsidian notes with in-note highlighting. - This plugin has not been manually reviewed by Obsidian staff.

↓ 38 downloadsUpdated 1mo agoMIT
Install in ObsidianView on GitHub

Vault Reader for Obsidian

Read long notes without leaving your vault.

Vault Reader demo

Vault Reader turns any Markdown note into a calm speed-reading panel beside your source note. Set your pace, pause and restart anytime, resume where you left off, and optionally highlight the current word in the note as you read.

Why Install It?

  • Review dense notes, essays, research, and meeting notes at a steady pace.
  • Keep the original Markdown visible while the reader runs beside it.
  • Control WPM, text size, panel zoom, accent color, and ORP focus.
  • Resume per-note progress or restart from the beginning.
  • Keep everything local: no accounts, telemetry, backend, or network calls.

What It Does

  • Side-panel reader: read beside the note instead of replacing it.
  • Playback controls: play, pause, stop, restart, and resume progress.
  • Reading controls: adjust WPM, text size, panel zoom, and ORP focus mode.
  • In-note highlight: optionally follow the current word in source mode.
  • Highlight colors: switch between yellow, orange, and blue.
  • Local-first design: no network calls, no account, no hosted backend, no telemetry.

Install

Install from Community Plugins:

  1. Open Settings -> Community plugins.
  2. Turn off Restricted mode if community plugins are not already enabled.
  3. Browse for Vault Reader.
  4. Install and enable the plugin.
  5. Open any Markdown note and run Vault Reader: Start reading current note.

Vault Reader is desktop-only for the first release.

How To Use

  1. Open a Markdown note.
  2. Run Vault Reader: Start reading current note.
  3. Use Play, Pause, Stop, and Restart.
  4. Adjust WPM with the buttons, number input, or ArrowUp / ArrowDown.
  5. Press Space while the reader panel is focused to play or pause.
  6. Toggle ORP, accent, text size, panel zoom, note highlight, and highlight color from the reader controls.

If you open a different note while the reader is still loaded, Vault Reader keeps the existing session and shows a Read current note action. This avoids silently losing your place.

Privacy And Security

Vault Reader does not collect telemetry, does not make network requests, does not require an account, and does not use a hosted backend.

The plugin stores settings and reading progress locally through Obsidian plugin data. It reads the active note only when you run the reader command or explicitly click Read current note.

See SECURITY.md and security-review.md for the public-review security contract.

Current Scope

  • Built for desktop Obsidian.
  • In-note highlight works best in source mode and may fall back to panel-only reading when exact mapping is unavailable.
  • Follow-scroll is intentionally not enabled, so playback does not force editor scroll/reflow on every token.
  • Selected-text reading is not a launch feature.
  • Mobile support is not validated yet.

For Developers

CI Release License: MIT

Local Testing

For local development or release-asset verification, use the included manual test vault:

  1. Install dependencies: npm ci
  2. Build and deploy into the test vault: npm run build:local
  3. Open this vault in Obsidian: fixtures/manual-test-vault
  4. Enable Vault Reader in Settings -> Community plugins.
  5. Open a test note such as 10-Prose.md.
  6. Run Vault Reader: Start reading current note from the command palette.

For a different local vault, set:

VAULT_READER_PLUGIN_DIR="/absolute/path/to/.obsidian/plugins/vault-reader" npm run build:local

Demo Asset

The README demo GIF is stored at docs/assets/vault-reader-demo.gif. Demo asset standards are documented in docs/assets/README.md. The GIF was captured from the curated manual test vault so public docs, QA, and launch assets all show the same tested experience.

Local Build + Deploy Pipeline

  • Deploy into the local manual test vault plugin folder: npm run deploy:local
  • Build then deploy in one step: npm run build:local
  • Watch mode with auto-deploy after each successful rebuild: npm run dev:local

Project Docs

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.