Viggo Meesters42 downloadsOpen .txt files as read-only text with line numbers, search navigation, filtering, and large-file guards.
TXT Viewer is a read-only plugin for inspecting .txt files with line numbers, search navigation, filtering, line-ending warnings, and large-file guards.
It is not a text editor. It is built for quick inspection of plain text exports, AI output, notes from other systems, and generated files where opening a raw text file is not enough context.
.txt files in a dedicated view.TXT Viewer renders the first 10,000 lines in normal text mode. Filter mode renders the first 1,000 matching lines. Additional lines are counted and reported in the status or warning area.
TXT Viewer does not make network requests and does not send vault content to external services. It does not use the system clipboard. It reads files through the vault API and renders a local view.
Plain text looks simple, but editing still creates risk around encodings, line endings, generated output, and accidental changes. TXT Viewer intentionally avoids writing to disk in v0.1.
TXT Viewer is prepared for Community plugin directory submission. Once accepted, it can be installed from Settings -> Community plugins -> Browse.
Until the community directory submission is accepted:
main.js, manifest.json, and styles.css from the latest release..obsidian/plugins/txt-viewer/.For beta testing, install the plugin with BRAT using this repository URL:
https://github.com/viggomeesters/obsidian-txt-viewer
Open any .txt file in your vault. The file opens with TXT Viewer.
Use the toolbar to:
npm install
npm run build
npx tsc --noEmit
npm test
For local development, copy or symlink this repository into .obsidian/plugins/txt-viewer/ inside a test vault.
Community plugin files are installed from GitHub releases. For each release:
manifest.json, package.json, and versions.json.npm install, npm run build, npx tsc --noEmit, and npm test.manifest.json.version.main.js, manifest.json, and styles.css as release assets.The repository includes a GitHub Actions release workflow with artifact attestation support. If GitHub Actions is disabled for the owner account, manual releases are still usable, but automated review may show a recommendation about missing artifact attestations.
The repository is prepared for Community plugin submission. The remaining submission step must be completed by the repository owner because it requires signing in, linking GitHub, and confirming the developer policies/support commitment.
Submit this repository URL:
https://github.com/viggomeesters/obsidian-txt-viewer
Steps:
Official references: