Last month a colleague sent me a ChatGPT export. Forty pages of research summary, saved as a markdown file. I double-clicked it at the end of a long day, expecting to read. Instead I got to watch my computer think.
Obsidian launched. It loaded the vault, all twenty-three of my community plugins, the theme, the workspace layout. It indexed the new file, added it to the graph, and helpfully suggested linking it to my notes on caching strategies, which had nothing to do with anything.
All I wanted was to read a document. I had accidentally enrolled it in my knowledge management system.
Let me say the thing I actually believe before going further: Obsidian is a wonderful tool, and I mean that without qualification. If you keep a vault, link your notes, tend your graph like a garden, you have my respect. This post is not about that.
It is about a narrower and increasingly common situation. Someone hands you a markdown file, and you just need to read it.
The Photoshop problem
Somewhere along the way, “open it in Obsidian” became the default answer to that situation. It is a strange default once you look at it directly. It is like being told to open Photoshop to view a JPEG.
Consider what actually happens when you double-click that file. Obsidian launches, which takes a few seconds if your vault is modest and longer if it is not. It loads your plugins, your theme, your workspace. It opens the file inside your system, which means the file is now in your recent files, your search index, your graph. You read the file. You close it. Your vault now contains a stranger, and it will remember the stranger until you clean house.
For a file you received, an export, a README from a repo you just cloned, a doc someone dropped in Slack, this is absurd overhead. You wanted to read a document. You got a workflow.
The plugins make it worse, and I say this as someone who likes plugins. Many serious Obsidian users run twenty or more of them. Each one is startup time. Each one is a potential conflict. Each one can break on update. All of it loaded and initialized, to render a single file.
What reading actually needs
Reading, it turns out, has modest requirements. Four of them.
Open instantly. Double-click, rendered document, under a second.
Render everything. Tables, code blocks, Mermaid diagrams, LaTeX, the full modern catalog. AI-generated documents use all of it, often in the same file.
Do not adopt the file. Reading something should not file it, index it, or ask where it belongs.
Disappear. When you are done, close it. No state to manage, no vault to maintain.
Obsidian fails three of these four by design. That is not a criticism. It is a different product. The failure is ours, for using a thinking tool to do a reading job.
Reading versus thinking
Because that is the real distinction, and it took me embarrassingly long to see it clearly. It is not Obsidian versus simple tools. It is reading versus thinking.
Reading is: someone gives you a document, you consume it, you move on. The tool should be invisible.
Thinking is: you develop ideas over time, connect concepts, build a body of knowledge. The tool should be powerful.
Using your thinking tool for reading is like using your workshop to open a letter. It works. But you have confused two activities, and you are paying the complexity cost of one to perform the other.
Lighter alternatives, honestly assessed
Meva does exactly this job: instant open, full rendering including Mermaid and LaTeX, live reload, no vault, no indexing, no account. Read-only by design. Free tier, and Pro is $14.99 once. (Yes, we make it. The bias is disclosed; the assessment stands.)
Marked 2 is the classic Mac preview tool. Fast and read-focused, very customizable. The interface shows its age, and it is weak on Mermaid and LaTeX. If your markdown is traditional, it is still good.
MacDown is free, open source, and lightweight. Fine for basic markdown. It will not handle AI-generated docs with diagrams.
Your browser, with a markdown extension, renders a dragged-in file with zero new software. Not beautiful, but functional in a pinch.
The terminal, via glow, renders markdown beautifully if you live in the terminal. The fastest option that exists, with no GUI at all.
VS Code preview is the Cmd+Shift+V you already have open. Not instant, not lightweight, but zero new tools.
When Obsidian is the right call
To be fair, there are reading situations where Obsidian wins outright. The file belongs in your vault permanently. You want to link it to other notes. You are going to annotate it and build on it over time. You are already in Obsidian and the file is already there.
In those cases the “overhead” is not overhead. It is the point. The vault is the workflow.
The kindest thing
I still open Obsidian every day. It is where my notes live, and it is good at being that place. I just no longer ask it to be the place where I read things that arrived from elsewhere.
The kindest thing you can do for a good tool is stop asking it to be a different one.
Meva is a fast, read-only markdown reader for Mac, Windows, and Linux. No vault, no plugins, no setup. Free at usemeva.com.
Related posts: - Why Meva Is Read-Only — the design decision behind it - Best Markdown Viewers for Mac in 2026 — honest comparison - Why AI Tools All Output Markdown — category explainer