Can I publish an Obsidian vault as a website with Flowershow?

Yes. Flowershow is built to publish a folder of Markdown files as a hosted website, and it explicitly supports Obsidian vaults. You point it at your vault folder, and your notes become a themed site with working wikilinks, backlinks, and an interactive graph. The main conditions: your notes need to be in a folder you can connect to Flowershow, and some features (custom domains, full-text search) are tied to the Premium tier according to the site's feature descriptions.

What carries over from your vault

Flowershow treats .md and .mdx files as pages, rendered with your site's theme and navigation. For Obsidian users, the relevant support is:

• Obsidian wikilinks — [[Note name]] style links resolve as site links rather than showing as raw text.
• Backlinks and graph view — the site describes "digital gardens" as being "mapped by backlinks and an interactive graph," which is the core Obsidian-style navigation experience.
• Rich Markdown — CommonMark, GFM tables and task lists, Mermaid diagrams, and LaTeX math are rendered.
• Obsidian Canvas and Bases — .canvas files become diagram pages, and Bases render as tables, cards, or lists.

Your files stay plain text, so the vault remains portable and Git-friendly. Flowershow describes itself as "infrastructure, not a silo" — you aren't converting notes into a proprietary format.

What doesn't automatically become a website

A few things to check before assuming a one-to-one match:

• Folder structure becomes site structure. Your vault's folders and note names determine page URLs, so a messy vault produces a messy site. Decide what should be public before publishing.
• Attachments need to be in the folder. Images, PDFs, .json, and .csv files are served at their own URLs, so linked attachments work only if they're inside the published folder.
• HTML files are served as written. If you have .html files, scripts run and relative links to CSS/JS/images work — useful, but it means raw HTML isn't themed like Markdown pages.
• Plugins aren't replicated. Obsidian community plugins that transform content won't run on Flowershow; only the Markdown features listed above are rendered.

How to publish, step by step

1. Prepare the folder. Confirm your vault (or the subset you want public) contains the notes and attachments you intend to publish. Keep private notes out of this folder.
2. Create an account. The site offers "Sign up with Google" and states the service is "free forever, no credit card required."
3. Connect or upload the folder. Flowershow's model is "one folder, any kind of site" — the folder you provide becomes the site.
4. Pick a theme. Four polished themes are available, or you can customize with CSS and Tailwind.
5. Verify the result. Open the published site and check that wikilinks resolve, the graph and backlinks appear, Mermaid/math render, and images load. This is the step where vault-specific issues surface.
6. Optionally add a custom domain. Custom domains, favicon, and social image are described as Premium features.

When Flowershow fits — and when it doesn't

If your priority is a public, link-rich garden of notes, Flowershow is a direct fit. If you depend on plugin-driven rendering or need search on a free tier, confirm those details on the pricing page before committing.