简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Flowershow?
Flowershow is a hosting service that turns a folder of Markdown and HTML files into a published website, without a build step or coding. You point it at files you already have, and it serves them as a themed site with navigation. The page describes it as infrastructure rather than a silo: your content stays as plain-text files that are portable and Git-friendly.
What it does with your files
.mdand.mdxfiles become pages styled by your chosen theme, with Obsidian-style wikilinks, Mermaid diagrams and LaTeX math rendered..htmlfiles are served as written, so scripts run and relative links to CSS, JavaScript, data and images work..json,.csv, images and PDFs are served at their own URLs so pages can load or link to them.- Obsidian
.canvasfiles become diagram pages, and Bases render as tables, cards or lists.
Who it suits
The page frames it around four uses: digital gardens (backlinks plus an interactive graph), blogs (themes, no site builder), wikis (automatic linking, search) and documentation sites (sidebar navigation, full-text search). A typical reader is someone who already writes in Markdown — often in Obsidian — and wants a public site without maintaining a static-site toolchain.
Trade-offs to weigh
Flowershow's simplicity comes from hosting, so you are depending on its platform rather than a self-managed build. Some features are gated: custom domains, favicons, social images and site-wide full-text search are described as Premium. The page advertises a free tier with no credit card, but check Flowershow pricing for current limits before committing.
If you already keep notes in a single folder, the practical next step is to publish one small folder first — an index page plus a few linked notes — and see whether the default theme and wikilink handling match how you write before moving a larger vault.
How do I publish an existing Obsidian vault as a website with Flowershow?
Keep the vault as a plain folder of Markdown and point Flowershow at it; the vault's notes become themed pages with wikilinks rendered as working links, and you can add HTML, images, CSVs, PDFs, Canvas diagrams and Bases alongside them in the same folder. There is no build step to run yourself.
A practical sequence
- Decide what goes public. A vault usually holds private notes. Work on a copy, or a subfolder you treat as the publishable set, so drafts and personal notes never reach the site.
- Check your links and embeds. Obsidian wikilinks are supported, as are Mermaid diagrams and LaTeX math. Attachments such as images and PDFs are served at their own URLs, so relative references keep working. Anything relying on a community plugin's custom syntax is the main thing to verify on a test publish.
- Publish, then look at the result as a reader. Navigate by backlinks and the graph if you want the garden feel, or check that a flat set of notes reads sensibly as a wiki. Search across pages is a Premium feature, so a large vault without it depends on good index notes and navigation.
- Add a custom domain, favicon and social image on Premium if this is a public-facing knowledge base rather than a personal garden.
What fits which vault
| Vault looks like | Best framing on Flowershow | Watch out for |
|---|---|---|
| Dense interlinked notes | Digital garden with graph and backlinks | Readers who expect a table of contents |
| Reference material you look things up in | Wiki with wired-up links | Finding pages without full-text search |
| Long-form writing | Blog with a polished theme | Obsidian-specific formatting in older notes |
| Mixed notes plus data and diagrams | One folder mixing Markdown, HTML, Canvas, CSV | Keeping private material out of the folder |
Decision criterion
If your vault is mostly private thinking with a few finished pieces, publish only those pieces rather than the whole vault; the tool makes either easy, but the editorial boundary is yours to set. If the vault is already a curated reference base, publish it whole and invest in an index page and consistent note titles instead.
For comparison, Obsidian's own publishing service is Obsidian and static-site generators like Hugo suit people who want a local build pipeline. As a next step, duplicate your vault, delete anything private, and publish that copy first.
Can I mix Markdown, HTML, and data files like CSV or PDFs in the same Flowershow site?
Yes. Flowershow is built around publishing a single folder that can hold different file types side by side, and each type is handled according to what it is.
How each file type behaves
- Markdown (
.md,.mdx) becomes themed pages with your site's navigation, and supports wikilinks, Mermaid diagrams and LaTeX math. - HTML (
.html) is served as written: scripts run, and relative links to CSS, JavaScript, data and images resolve correctly. This is useful for an interactive chart or a one-off page you already have. - Data, images and PDFs (
.json,.csv, images, PDFs) are served as files at their own URLs, so Markdown or HTML pages can link to them or load them at runtime. - Obsidian Canvas (
.canvas) files become diagram pages, and Bases render as tables, cards or lists.
A concrete example
A small research site could look like this:
my-site/
index.md → themed landing page
notes.md → page with wikilinks and math
report/index.html → interactive HTML report with its own JS
data/sales.csv → downloadable or fetchable data
images/cover.png → linked from pages
A reader lands on index.md, follows a wikilink to notes.md, and downloads data/sales.csv from a link on either page—all under one domain and theme.
Trade-offs to weigh
| Approach | Strength | Watch out for |
|---|---|---|
| Markdown pages | Theme, nav, search and wikilinks apply automatically | Less control over bespoke layout |
| Raw HTML | Full control; existing pages work unchanged | You maintain styling and navigation yourself |
| Linked data/PDF files | Simple, direct URLs for downloads or fetches | Not rendered as pages; readers leave the themed view |
If most of your content is notes or docs, keep it in Markdown and reserve HTML for the few pages that need custom behaviour. If you are migrating an existing HTML site, you can drop it in alongside new Markdown rather than rewriting it.
Next step: sketch your folder structure first, decide which pages truly need HTML, then check the publishing workflow and plan options on Flowershow.
What features are included in the free Flowershow plan versus the paid Premium plan?
The page itself does not publish a feature-by-feature comparison of the free and Premium plans. It states that Flowershow is "free forever, no credit card required," and separately marks three capabilities as Premium: custom domains (with your own domain, favicon and social image), full-text search across every page, and — implicitly, since they are grouped under "Premium" — the branding controls that come with a custom domain. Everything else described on the page is presented as part of the product without a plan label, so treat it as likely available on the free tier rather than confirmed.
What the page labels Premium
| Feature | What it does | Who cares |
|---|---|---|
| Custom domain | Serve the site from your own domain instead of a Flowershow subdomain | Anyone publishing under a brand, a business or a portfolio |
| Favicon and social image | Control the browser tab icon and link-preview image | People sharing links on social media or in chat apps |
| Full-text search | Search across every page of the site | Wikis, docs and large note gardens where readers need to find things fast |
What appears to come with the site itself
- Publishing a folder of Markdown (
.md,.mdx) as themed pages with navigation, wikilinks, Mermaid diagrams and LaTeX math. - Serving
.htmlfiles exactly as written, with scripts running and relative links to CSS, JavaScript, data and images working. - Serving JSON, CSV, images and PDFs as files at their own URLs.
- Obsidian Canvas files rendered as diagram pages, and Bases rendered as tables, cards and lists.
- Four themes plus custom CSS and Tailwind for full control of appearance.
- Plain-text files that stay portable and Git-friendly, with no lock-in.
How to decide
If you are publishing a personal digital garden or a small blog and a Flowershow-hosted address is fine, the free plan covers the publishing workflow described on the page. Upgrade thinking usually starts at the moment a link needs to look like your own brand, or when a site grows past a handful of pages and readers start hunting for a search box. For a documentation site with dozens of pages, search is the feature most likely to justify Premium on its own; for a one-page report, it is irrelevant.
A practical next step: build a three-page test site — one Markdown page, one HTML page with a linked stylesheet, and one image — and confirm the free tier handles the mix before committing content. Check the plan details on Flowershow's pricing page for the current split, since the marketing page does not enumerate it.
How does Flowershow handle backlinks, wikilinks, and the interactive graph for digital gardens and wikis?
Flowershow treats backlinks, wikilinks and the graph as built-in parts of a "digital garden" or wiki site rather than plugins you assemble. According to the site, Obsidian-style wikilinks "just work" in Markdown, and for gardens the notes are "mapped by backlinks and an interactive graph." For wikis, links are described as "wired up automatically." In practice, this means you write [[Note name]] in your Markdown, and Flowershow resolves it into a real link to that page and records the reverse connection, so each note can show what links to it.
What this suits
- Obsidian users: If your vault already uses wikilinks, you can point Flowershow at the folder and keep writing the same way instead of converting links to standard Markdown URLs.
- Personal gardens: The graph view helps you see clusters and orphan notes, which is useful when browsing rather than searching for something specific.
- Small wikis: Automatic linking and the graph give a navigable structure without hand-building a sidebar or index for every topic.
Trade-offs to weigh
- Graph value depends on density. A garden with a handful of notes produces a sparse, not very informative graph; it becomes useful as notes and links accumulate.
- Wikilinks are convenient but less portable than standard Markdown links. The site stresses that your files stay plain text and Git-friendly, but if you later move to a tool that doesn't understand
[[...]]syntax, those links may need converting. - Search is separate. The site lists full-text search as a Premium feature, so on a free site readers rely more on links and the graph to find their way around.
A concrete scenario
Suppose you keep a research vault with notes on methods, sources and open questions. Publishing it as a garden means a reader landing on "Interview method" can follow wikilinks to related sources, see which notes link back to it, and use the graph to spot an under-connected topic worth developing.
Next step: publish a small test folder containing three or four interlinked notes and check that wikilinks resolve and backlinks appear before committing a larger vault. If you want to compare approaches, Obsidian documents its own graph and backlink behavior for local vaults, which is a useful baseline for judging what you need online.
Can I use a custom domain and full-text search on a Flowershow site?
Yes—both are available, but they sit on the paid tier. Flowershow's page lists custom domains (with your own favicon and social image) and full-text search across every page as Premium features, while the free-forever plan requires no credit card. So if you need a branded address like yourdomain.com or readers who search a large wiki or docs set, plan on Premium; if you only want to publish a small garden or one-page report, the free tier covers the core publishing.
What each feature actually changes
- Custom domain: Your site appears under your own address instead of a Flowershow subdomain, and you control the favicon and social preview image. This matters most for docs, company wikis or portfolios where the URL is part of the brand. The trade-off is setup: you'll point DNS records at Flowershow, so budget a little time and access to your domain registrar.
- Full-text search: A search box indexes every page, which is the difference between a browsable set of notes and a usable knowledge base. It's most valuable once you have dozens of pages; for a five-page site, sidebar navigation usually does the job.
A concrete scenario
Say you keep an Obsidian vault of internal processes and want colleagues to find answers without cloning the vault. Publish the folder, add a custom domain like handbook.yourcompany.com, and enable search so someone can type "expense policy" and land on the right note. Without Premium, the site still works—you'd share the Flowershow URL and rely on navigation and backlinks instead of search.
Decision criterion
Choose Premium when at least one of these is true: the URL is customer- or colleague-facing, or your content exceeds roughly 20–30 pages where search saves real time. Otherwise start free, confirm the publishing workflow suits you, and upgrade later—since your files stay plain Markdown, nothing is locked in.
For a broader look at Markdown-based publishing options, Obsidian covers the vault side, and Astro is a code-first alternative if you later want full control over hosting and search.
Cloudflare
Vercel
User reviews (0)