Website 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 Leaflet?
Leaflet is a publishing platform for writing a blog, sending a newsletter, or running another kind of ongoing publication, with distribution built in: posts can go out by email, to Bluesky, and across the wider "Atmosphere" social ecosystem. Its pitch is a combination of familiar blogging tools — drafts, post management, subscription analytics, settings — with free custom themes and custom domains, plus collaborative editing for writing with others.
Where it fits
Leaflet suits writers who want a home for their work but don't want to run a newsletter tool and a blog separately. The page's examples show the range: personal journals, link roundups, music writing, commentary on politics and philosophy, updates from a software project, and notes on the open social web. Most are individual voices publishing regularly to a small audience rather than large media operations.
The practical trade-off is reach versus ownership. Publishing into a social ecosystem means your posts can find readers where they already are, instead of waiting for them to subscribe. The cost is that your audience and your workflow are tied to that ecosystem and to Leaflet's tooling, so it's worth checking how easily you could export posts and subscriber contacts before committing years of writing.
A concrete case
Say you write a weekly essay and also post short reactions on Bluesky. Instead of maintaining a separate newsletter service and cross-posting by hand, you draft in Leaflet, publish once, and let it go out by email and to social readers. The free tier is the sensible place to test whether the writing and distribution flow suits you; the site also lists a Pro plan, so compare what it adds against your needs once you know you'll keep publishing.
To judge fit, read two or three of the listed publications and ask whether they look like what you want to make.
How does Leaflet distribute my posts to Bluesky and the Atmosphere?
Leaflet's page describes sending updates via Email, Bluesky, and the Atmosphere as one of its publishing features, and it positions that reach as part of a broader "social ecosystem with millions of users." In practice, that means a post written in Leaflet can be pushed out as an email update to subscribers and as a social post rather than living only on your own site.
What the page supports
- Three stated channels: Email, Bluesky, and the Atmosphere.
- Subscription tracking: the page lists analytics and subscription management alongside drafting and publishing, so you can see who has signed up.
- A social identity: the example writers listed on the page appear with handles on Bluesky and other Atmosphere-adjacent domains, suggesting your publishing identity is tied to an account you already hold there.
What it does not say
The page does not explain the mechanics — whether a Bluesky post is a full copy, a link card, or a short teaser, whether cross-posting is automatic or per-post, or how threading and replies behave. Treat those as things to confirm in the product itself before relying on them.
A practical scenario
Suppose you run a small newsletter and also post on Bluesky. You write once in Leaflet, and the same piece reaches email subscribers and your Bluesky followers without a second drafting pass. The trade-off is duplication: a long essay that reads well in an inbox may feel heavy in a Bluesky feed, so many writers keep the social version short and let the email carry the full text.
As a next step, publish one test post and check all three surfaces — inbox, Bluesky, and the Atmosphere view — to see how the copy is rendered before committing a real issue. For comparison, Leaflet is the reference point here; established newsletter tools like Buttondown and open-social publishing via Bluesky itself are worth reviewing if cross-posting fidelity matters more to you than a single drafting surface.
Can I use Leaflet to send email newsletters to subscribers?
Yes. Leaflet is built for exactly that: its page describes sending updates via email alongside Bluesky and the broader Atmosphere, and it lists newsletters as a core part of building a community. You write and manage posts in one place, track subscriptions, and use analytics to see how they perform.
Who it suits
- Independent writers and bloggers who want a blog and a newsletter from one tool rather than stitching together a site, an email service and a social account.
- Creators already active on Bluesky who want each post to reach subscribers by email and on the social web at once, instead of copy-pasting between platforms.
- Small collaborative teams — the page advertises collaborative editing and easy sharing, which helps if a co-writer or editor is involved.
Trade-offs to weigh
- Open-social reach vs. inbox deliverability. Cross-posting to Bluesky is convenient, but email still does the heavy lifting for people who don't use that network. Check that subscribers can manage preferences and that you can export your list, so you aren't locked in.
- Simplicity vs. deep email tooling. Leaflet presents itself as simple publishing. If you need advanced segmentation, drip sequences or detailed A/B testing, compare against a dedicated newsletter service before committing.
- Customisation. Free custom themes and custom domains are offered, which is unusual at the free tier and useful if you want the newsletter to look like your own site.
A practical next step
Pick one piece you'd normally publish as a blog post and one short update, publish both through Leaflet, and see how the email version reads on a phone. If the formatting and signup flow feel right for your audience, move your list over; if you rely on complex automation, keep a specialist email tool for those campaigns.
What do I get with Leaflet Pro compared to the free plan?
Leaflet's page advertises a Pro plan alongside a free tier, but it does not spell out the Pro feature list or limits in the material available, so the exact differences aren't confirmed here. What the page does establish is the free plan's baseline and the overall feature set that Pro presumably builds on.
What the free plan covers
The page says "Leaflet is free for everyone" and lists "fast, powerful text editing" as part of that free tier. The broader publishing toolkit — drafting and managing posts, tracking subscriptions, sending updates via email, Bluesky and the Atmosphere, free custom themes and custom domains, and collaborative editing — is presented as part of the platform generally, not clearly assigned to one tier.
What to check before upgrading
Because the page separates Pro only through a "Get Pro" checkout link, confirm these points on the pricing section itself:
- Limits: subscriber count, number of posts, or storage caps on free versus Pro.
- Custom domains and themes: whether these are free as stated or Pro-only in practice.
- Email/newsletter sending: volume allowances, since email delivery is usually the first thing metered.
- Analytics depth and collaboration seats: whether Pro adds more than the free tier.
A practical way to decide
If you're starting a personal blog or link digest — the kind of writing shown in Leaflet's examples, such as link dumps or personal essays — begin on the free plan and upgrade only when a specific limit blocks you, such as needing a custom domain or exceeding a sending cap. For a newsletter with a growing list, compare the Pro price against dedicated newsletter tools like Buttondown or Substack before committing, since delivery limits and audience tools are where the real trade-offs sit.
How does collaborative editing work on Leaflet for writing with others?
Leaflet's own feature list describes collaborative editing and easy sharing as part of its publishing toolkit, but it gives no detail on how that collaboration actually works—whether co-authors edit simultaneously in the same draft, whether you invite people by link or account, or what permissions exist. So the honest answer is that co-writing is a stated capability, not a documented workflow.
What to expect in practice
- Shared drafts before publishing. The natural reading is that collaborators work on a post inside Leaflet before it goes out, rather than after.
- Sharing tied to your audience tools. Leaflet pairs collaboration with newsletters, events and conversations, so sharing a draft may overlap with how you already reach subscribers.
- A social layer alongside. Publishing can go out via Email, Bluesky and the Atmosphere, which matters if your co-writers are already active there rather than on Leaflet itself.
A concrete scenario
Two people run a small newsletter: one drafts, the other edits and fact-checks. If Leaflet supports shared drafts, the editor can refine copy before the send; if it only supports sharing a finished post, you'd need to draft elsewhere and paste in. That distinction decides whether Leaflet replaces your current document workflow or sits on top of it.
How to check before committing
- Start a free draft and look for an invite or share control on the post itself.
- Test with a second account to see whether edits appear live or only after saving.
- Confirm what a collaborator can do—comment, edit, or publish.
- Compare with tools built around co-writing, such as Google Docs, if simultaneous editing is essential.
For a single writer who occasionally hands a draft to one editor, Leaflet's stated sharing may be enough. For a team that needs live multi-cursor editing and version history, verify those specifics first—or keep drafting in a dedicated editor and use Leaflet for distribution.
Can I connect a custom domain and theme to my Leaflet blog?
Yes. Leaflet's page lists "Free custom themes and custom domains" as part of the publishing package, so a custom domain and a theme aren't locked behind the Pro plan.
What that means in practice
- Custom domain: You can point your own address (say,
yourname.com) at your Leaflet blog instead of publishing on aleaflet.pubsubdomain. The writer sites shown on the page—such as@aaronrosspowell.comand@catabush.com—use their own domains, which suggests this is a normal, supported setup rather than an edge case. - Custom themes: You can change how the blog looks rather than accepting a single default layout. The page doesn't spell out whether themes are built from templates, CSS, or both, so check the theme options inside Settings after signing up.
- Both together: The two features are listed side by side, which implies you can combine them—a themed blog served on your own domain.
A useful next step
Before committing, decide what you need the domain for. If it's a personal blog or newsletter that may later move to another platform, keep your domain registrar separate from Leaflet and use DNS records to connect it, so the address stays yours. Then open Settings, connect the domain, and apply a theme—test the result on a phone, since theme choices often look different at narrow widths.
For comparison, other publishing tools handle this differently: WordPress.com ties some domain and theme options to paid tiers, while Ghost has offered self-hosting for full control. If owning the underlying setup matters to you, weigh Leaflet's simplicity against that kind of control. You can see how Leaflet presents these features at Leaflet.
User reviews (0)