Aki93 downloadsExport selected notes and Bases views to a self-contained offline website — shareable as a folder, encrypted ZIP, or password-protected web package.
Export selected Obsidian content — including Bases views — to a self-contained, offline-readable static website. Share it as a plain folder, an AES-encrypted ZIP, or upload it to any ordinary web host, optionally behind a password.

.base pages and ![[File.base#View]]
embeds (with this-context evaluation), named views, groups, formula
columns, displayName headers, summaries (totals + per-group), table /
list / cards views with cover images.| Mode | What you get |
|---|---|
| Local folder | a normal offline folder — open START_HERE.html |
| Encrypted ZIP | AES-256 archive (password required before extraction) |
| Web: Public | uploadable folder, indexable by search engines |
| Web: Link-only | unguessable folder name, noindex everywhere, no referrer leakage — "anyone with the link" sharing |
| Web: Password | a generated PHP login gate (bcrypt, sessions, path-traversal safe) for ordinary Apache/PHP shared hosting, with a built-in host self-check page |
BASE badges,
current-page highlight); collapses to a menu button on mobile.file://, no CDN, no
fonts to fetch, no framework. Design tokens (CSS custom properties) make
re-theming a single-file edit.obsidian:// deep links are stripped from
shared output.
Export (choose scope)... from the command
palette -> pick a scope (all Bases / entire vault / a folder / one Base /
the open note) -> pick an output mode -> optionally set a custom title.... menu on a note / Base, to export just
that item..base files live.
Upload the whole exported folder to your host. Opening the folder URL shows a
login page; run the self-check link at the bottom first — it verifies the
host actually blocks direct access to the private folder before you share the
link. Requires Apache with .htaccess + mod_rewrite and PHP sessions
(typical WordPress-grade shared hosting).
Security model, honestly: Link-only mode reduces discoverability; it is not access control. Password mode gates web access; it does not encrypt files at rest and does not protect content from the hosting provider. The encrypted ZIP protects the archive — extracted files are normal files.
Exported links and task icons follow your Obsidian accent color (captured at export time).
VaultPack makes network requests only during an export, and only to build offline embed cards for external content found in your notes:
youtube.com/oembed + the video thumbnail (bundled into the package)publish.twitter.com/oembed for tweetsNo telemetry, no analytics; nothing about your vault is transmitted anywhere. Exports work offline too — external embeds then degrade to plain link cards.
npm install
npm run build # type-check + bundle main.js
The repository ships a checker (scripts/check-export.mjs in the parent
project) and headless test harnesses under test-harness/.
LICENSE).src/checkbox-icons.ts.