TL;DR - Obsidian is a good place to write and
organize Markdown notes locally. When the job is "get this note out of the
vault as a document," the rule is simple: use Obsidian's own PDF export for
quick personal copies, and use depapel when the recipient
needs a cleaner shareable PDF or a DOCX for review.
You do not usually feel the export problem while you are still inside
Obsidian.
The note looks fine in the vault. Links work. The theme matches your setup. The
Markdown stays in local files, which is one of the main reasons people use
Obsidian in the first place. According to
Obsidian's own docs, notes live as
Markdown-formatted plain text files inside a local vault.
The problem starts when somebody outside that workflow asks for a file.
A client wants the note in email. A teammate wants a PDF they can read on a
phone without installing anything. A reviewer wants a Word doc with comments.
That is the moment when "great note app" and "good export workflow" stop being
the same thing.
The practical decision
Use Obsidian export when:
- you want a quick PDF of one note,
- you are happy with the note as it looks in Obsidian,
- and the export is mostly for your own use or an informal share.
Use depapel when:
- the file is going to someone outside your vault workflow,
- output quality matters more than "print what I see right now",
- you want PDF and DOCX from the same Markdown source,
- or you want to paste Markdown, upload a
.md file, or import from a public
Git URL and hand off a cleaner document.
That is the honest split. Obsidian is the writing environment. depapel is the
export step.
Why Obsidian is still the right place to write
This is not a case against Obsidian. It is the opposite.
Obsidian is attractive because the source stays yours:
- notes are plain Markdown files,
- the vault stays on your local file system,
- internal linking makes long-term note organization better,
- and the app is much stronger at knowledge-base workflow than a converter
should be.
If your job is thinking, drafting, and organizing notes, keep doing that in
Obsidian.
The export question only appears when the note needs to travel.
A small example that exposes the difference
The raw Markdown for a lot of exported notes is not complicated. It often looks
more like this:
# Launch Note
## Summary
Ship the updated onboarding guide as a shareable PDF.
## Checklist
- [x] Finalize copy
- [x] Review screenshots
- [ ] Send document to stakeholders
## Handoff
| Output | Use when |
|---|---|
| PDF | The document should look fixed |
| DOCX | The reviewer wants comments and edits |
This is simple Markdown. But it still asks the export path to handle headings,
a checklist, and a table cleanly.
If the result is just a quick snapshot for yourself, Obsidian's export may be
enough.
If the result needs to feel like a document you can send confidently, the
layout rules matter more.
Where the export gap shows up
The difference is usually not "can this become a PDF at all?" It is "what kind
of PDF do I get?"
The export gap shows up when you care about things like:
- keeping headings with the content they introduce,
- avoiding awkward splits in lists or tables,
- choosing a document theme separately from your vault theme,
- exporting DOCX from the same source,
- or producing a file that feels like a deliberate handoff rather than a
printed app view.
That is where a Markdown-to-document tool can add value without trying to
replace the note app.
A side-by-side example
The comparison below uses the same Markdown source and shows the exact kind of
output difference people notice when a note becomes a file for sharing. The
source is the public markitdown README.
Where depapel fits
depapel is a fit for the second half of the workflow:
- Write and organize the note in Obsidian.
- When it is time to share, paste the Markdown into depapel, upload the
.md
file, or load a public Git URL.
- Export PDF when the file should look fixed.
- Export DOCX when the recipient needs comments or edits.
That gives you a cleaner split of responsibilities:
- Obsidian for the vault, note graph, and authoring workflow.
- depapel for PDF/DOCX export and document-style handoff.
Honest tradeoffs
Use Obsidian instead when:
- the note should stay inside your personal vault workflow,
- the built-in export already looks good enough for the job,
- or you do not need DOCX or extra export control.
Use depapel instead when:
- sharing is the real job,
- the recipient is not an Obsidian user,
- you want PDF and DOCX from the same source,
- or you want a Markdown-first export step without building a local publishing
setup.
depapel is not your knowledge base. It does not replace backlinks, vault
navigation, or local note-taking. It is the export layer.
Final rule to remember
Write in Obsidian because it is a strong local Markdown workspace.
Switch to depapel when the note stops being "a note in my vault" and becomes "a
document I need to hand to someone else."
That is the cleanest way to think about the two tools: one is where the
Markdown lives, and the other is where the shareable file gets made.
Please enable JavaScript to use depapel.