Step 1 — Export your files from Repage
Three ways, depending on how much you want:
- One document: open it and click the
.md/.htmldownload button in the viewer toolbar. Markdown notes also have an Obsidian button that sends the note straight into your vault — no zip needed. - One project: click the download icon next to the project in your dashboard (or Export .zip on the project page) to get the project as a folder of source files.
- Everything: use Download everything (.zip) at the bottom of your workspace — one archive, one folder per project, loose documents at the root.
Step 2 — Unzip into a vault
- Unzip the export anywhere you like.
- In Obsidian, choose Open folder as vault and pick the unzipped folder — or drag the folders into an existing vault.
Your Repage projects appear as folders, and every Markdown document opens natively — backlinks, graph view, search, everything Obsidian does. No conversion happened and none was needed: Repage stores your Markdown source exactly as you wrote it.
Step 3 — Install the HTML Reader plugin for HTML documents
Documents you published as HTML (dashboards, styled reports, interactive pages) export as .html files, which Obsidian can't open out of the box. The free community plugin HTML Reader fixes that:
- In Obsidian, open Settings → Community plugins and turn off Restricted mode if it's on.
- Click Browse, search for “HTML Reader” (by Nuthrash), and click Install.
- Click Enable. That's it — any
.htmlor.htmfile in your vault now opens inside Obsidian when you click it.
By default the plugin sanitizes what it renders (scripts and unsafe markup are stripped), which is a sensible setting for files from anywhere. Since these are your own documents, you can relax the mode in the plugin's settings if a dashboard needs its interactivity.
Markdown or HTML — which should you publish?
- Markdown for anything you might want in Obsidian long-term: plans, notes, journals, specs. It's Obsidian-native with zero plugins.
- HTML for custom layouts and interactivity: dashboards, calculators, styled reports. Obsidian renders these via HTML Reader; browsers render them anywhere.
Either way the export preserves your source byte-for-byte — Repage never converts or locks your content. If Repage disappeared tomorrow, your vault wouldn't notice.
A library that works in Repage and Obsidian
Publish and share from Repage; export to plain files whenever you want.
Publish a documentFrequently asked questions
- Do I need a plugin to read my Markdown documents in Obsidian?
- No. Repage exports Markdown documents as plain .md files, which Obsidian opens natively. The plugin is only needed for documents you published as HTML.
- Which plugin opens HTML files in Obsidian?
- The free community plugin "HTML Reader" (by Nuthrash). Install it from Settings → Community plugins → Browse, search for "HTML Reader", then Install and Enable. After that, clicking any .html file in your vault opens it inside Obsidian.
- Is it safe to open exported HTML in Obsidian?
- HTML Reader sanitizes documents by default (its restricted modes strip scripts and unsafe content), so styled reports and dashboards render while risky markup is removed. You can relax this in the plugin's settings if you trust the files — they're your own documents.
- Does Repage convert HTML documents to Markdown on export?
- No — exports preserve the original source exactly, so nothing is lost in translation. Markdown stays .md and HTML stays .html. If you want a document to be Obsidian-native, publish it as Markdown; HTML is best for dashboards and interactive pages.
- Will my Repage projects become Obsidian folders?
- Yes. The account export (and each project export) is a zip with one folder per project, so your Repage organization carries over as vault folders one-to-one.