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 Linwood Butterfly?
Linwood Butterfly is a free, open-source note-taking and drawing app built around an infinite canvas. Instead of constraining ideas to a fixed page, it lets you handwrite, sketch, annotate, and arrange content freely, then keep editing it later. The project describes itself as "a workspace for visual thinkers" and runs on Android, Windows, macOS, Linux, and in a browser, with an iOS preview also available.
H3 What you can actually do with it
The core appeal is mixing media in one document. You might, for example, capture lecture notes with a stylus, drop in a PDF and mark it up, sketch a rough interface, and add a diagram — all on the same canvas. Drawing works with a stylus, touch, or mouse, and stroke width, color, smoothing, and texture are adjustable. If a mark is wrong, you edit it rather than undoing everything.
Beyond pen and eraser, the toolset includes labels, shapes, polygons, rulers, grids, textures, stamps, a laser pointer, and presentation tools.
H3 Where it differs from a simple sketch app
| Aspect | What Butterfly offers |
|---|---|
| Canvas | Infinite, not page-bound |
| Elements | Stay editable — move, resize, recolor, reorganize after placing |
| Imports | Camera photos, gallery images, PDFs, SVGs |
| Reuse | Templates plus packs, stamps, palettes, and styles shared across documents |
| Files | Documented .bfly and .tbfly formats |
H3 Ownership, sync, and collaboration
Documents are local by default and work offline; they stay on your device unless you choose otherwise. You can connect WebDAV services such as Nextcloud for sync and backup. Collaboration is experimental and uses end-to-end encrypted sessions through Swamp or a WebSocket server you host yourself. The software is licensed under GNU AGPL-3.0.
H3 A practical next step
If you are deciding whether to try it, pick one real task first — annotating a PDF for a class, or sketching a layout for a project — and test whether the infinite canvas and editable elements save you time compared with your current app. Because it is open source and local-first, it suits people who want their notes on their own device and are willing to run their own sync or collaboration setup. If you need polished, managed real-time collaboration out of the box, that part is still experimental here.
You can download it or try the web app at Linwood Butterfly.
Can I use Linwood Butterfly offline without an internet connection?
Yes. Butterfly is built to work locally by default: documents live on your device, and you can keep writing, sketching, and annotating without an internet connection. You only involve the network if you choose to sync or back up, for example by connecting a WebDAV service such as Nextcloud.
What this looks like in practice
- On a laptop or tablet, open Butterfly and start a new canvas; no account or connection is needed to capture notes or draw.
- Save your work in Butterfly's documented
.bflyor.tbflyformats so files stay portable and editable on the same device. - If you later want the same notes on another machine, that is the point where you set up WebDAV sync or move files manually.
Trade-offs to know
- Offline-first means your device is the source of truth. If the device is lost or its storage fails, unsynced work is gone, so a backup routine matters.
- Collaboration features are experimental and depend on a server (Swamp or a WebSocket server you host), so they are not an offline activity.
- The browser version naturally needs the page loaded first, though it can continue working after that; installed desktop and mobile builds are the more dependable choice for disconnected use.
Next step: install Butterfly on the device you actually carry to class or meetings, create one test document, then close your Wi-Fi and confirm you can reopen and edit it. If that works, add WebDAV sync as a separate backup layer rather than as your only copy. Butterfly is free and open source under the GNU AGPL-3.0 license, so you can also verify the local-storage behavior yourself.
How do I sync and back up my Butterfly notes across devices?
Butterfly treats sync as something you bring yourself rather than a built-in account service. Documents are local by default, so cross-device sync means pointing the app at storage you control.
What Butterfly gives you
- Local-first storage. Your documents live on your device unless you save them elsewhere, and you can keep working offline.
- WebDAV support. The site names Nextcloud as a WebDAV service you can connect to sync, back up, and edit notes anywhere.
- Document formats. Files are kept in the documented
.bflyand.tbflyformats, which matters for backup because you are copying ordinary files, not an opaque database. - Optional collaboration. Experimental end-to-end encrypted sessions run through Swamp or a WebSocket server you host yourself. That is live collaboration, not the same thing as backup.
A practical setup
- Pick a WebDAV provider or run your own. Nextcloud is the reference example Butterfly names; any standards-compliant WebDAV endpoint should behave similarly.
- Connect it in Butterfly's settings and choose a folder as your sync target.
- Install Butterfly on each device and point them at the same folder.
- Keep a second, independent copy — a scheduled copy of that folder to external storage or another cloud — so a bad edit or a broken sync does not propagate everywhere.
Trade-offs to weigh
| Approach | Good for | Watch out for |
|---|---|---|
| WebDAV sync to your own server | Control, offline use, no vendor lock-in | You run and maintain the server |
Manual file copies of .bfly files |
Simple, versioned backups | No automatic merging across devices |
| Hosted WebSocket / Swamp sessions | Live co-editing | Not a backup; sessions are experimental |
If you only need one device at a time, manual copies to a synced folder may be enough. If you edit on a tablet and a laptop in the same day, WebDAV is the more comfortable route — but confirm how your client handles two devices editing the same file, since conflicting writes are the usual weak point in any file-based sync.
Next step: open Butterfly's settings on your primary device, connect your WebDAV folder, create one test note, and verify it appears on a second device before moving your existing documents over.
Is Linwood Butterfly free and open source, and what file formats does it use?
Yes. Linwood Butterfly is free and open source under the GNU AGPL-3.0 license, and it uses its own documented formats: .bfly and .tbfly.
What that means in practice
- Cost: The page describes Butterfly as free and open source, so there is no paid tier described in the supplied information.
- Licensing: AGPL-3.0 is a strong copyleft license. If you only use Butterfly for note-taking or drawing, that mainly matters as a guarantee that the source is available and the software can be modified and redistributed under the license terms. If you plan to modify Butterfly and offer it as a network service, the AGPL's source-sharing requirements are worth reviewing carefully.
- File formats:
.bflyis the main document format, and.tbflyis also documented. Because these are Butterfly-specific formats, they are the natural choice if you want to keep every element editable. For sharing with people who do not use Butterfly, export to common formats is the practical route.
Choosing a format
| Situation | Sensible choice |
|---|---|
| Continuing to edit notes, sketches, and layers in Butterfly | .bfly |
| Working with a variant or template-style document | .tbfly |
| Sending work to someone without Butterfly | Export to a common format |
| Archiving for the long term | Keep the original .bfly alongside any export |
The trade-off is straightforward: native formats preserve editability, while exports maximize compatibility. Keeping both is usually the safest habit.
Next step
If you are evaluating Butterfly, download it or open the web app, create a short test document, and save it once as .bfly. Then export the same document to a common format and open both again. That quick check shows you whether the editing fidelity and export quality match how you actually work. You can also review the documentation and blog for format details as your projects grow.
Which devices and platforms can run Linwood Butterfly?
Linwood Butterfly runs on Android, Windows, macOS, Linux, and in a web browser. An iOS preview is also available, so iPhone and iPad users can try it but should treat it as unfinished rather than a fully supported release.
What that means in practice
- Desktop: Windows, macOS, and Linux builds suit long note-taking, diagramming, or PDF markup sessions with a mouse or drawing tablet.
- Mobile: Android is the mature mobile option, useful for stylus notes in class or quick sketches on the move.
- Browser: The web app lets you open a canvas on a machine where you cannot install software, though offline local-first behavior is the point of the downloadable versions.
- iOS: Preview status means features may lag behind other platforms and bugs are more likely.
Choosing between them
| Situation | Sensible choice |
|---|---|
| Stylus lecture notes on a tablet | Android app |
| PDF markup and diagrams at a desk | Windows, macOS, or Linux |
| Borrowed or locked-down computer | Web app |
| iPad as your main device | iOS preview, with a desktop fallback |
Because documents live on your device by default and can sync through WebDAV services such as Nextcloud, you can start a sketch on one platform and continue on another without changing tools. If you want a stable daily driver today, pick Android or a desktop build; if you mainly want to test the canvas on an iPad, try the preview first and keep the web app as a backup. More detail is at Linwood Butterfly.
How can I collaborate with others on a Butterfly canvas securely?
Butterfly's collaboration is experimental, and its security model is built on end-to-end encryption (E2EE). You host or choose the relay, so the server passes encrypted data between participants rather than reading it.
What the page actually supports
- E2EE sessions: collaboration runs through encrypted sessions, not a plain shared document link.
- Two connection routes: a Swamp session, or a WebSocket server you host yourself.
- Self-hosting is the point: because you control the WebSocket server, you avoid handing your canvas to a third-party service.
- Local-first baseline: documents live on your device unless you deliberately save them elsewhere (for example, syncing to your own WebDAV storage such as Nextcloud).
Practical secure setup
- Install or open Butterfly on each participant's device (Android, Windows, macOS, Linux, or the browser).
- Decide on the transport: quickest is a Swamp session; strictest control is your own WebSocket server on a machine you administer.
- If self-hosting, put the server behind TLS (wss://) and restrict who can reach it — a private network, VPN, or firewall allowlist rather than the open internet.
- Share the session details only through a channel you already trust, and keep the participant list small while the feature is experimental.
- Keep a local copy of the
.bfly/.tbflyfile as your source of truth, so a failed session never costs you work.
Trade-offs to weigh
| Approach | Who controls the data | Best for |
|---|---|---|
| Swamp session | Relay operator, but content stays encrypted | Fast, low-setup sessions |
| Self-hosted WebSocket | You | Sensitive work, classes, internal teams |
| WebDAV sync only | Your own storage provider | Backup and multi-device editing, not live co-editing |
A concrete scenario
A small design team sketching a UI flow: one person hosts a WebSocket server on an office machine, the others join over the LAN, and everyone keeps a local file. The encryption protects the drawing in transit; the self-hosted server keeps the session off public infrastructure. If a teammate is remote, a VPN is the simplest way to reach that server without exposing it.
Decision criterion
Choose Swamp when convenience matters and the content is not highly sensitive. Choose a self-hosted WebSocket server when you need to know exactly where the traffic goes. If you only need to move work between your own devices, skip live collaboration and sync via WebDAV instead.
Because collaboration is labelled experimental, treat it as a convenience layer on top of a local-first workflow rather than the place your only copy lives. Start by testing a session with one colleague on a throwaway document before relying on it for anything important.
User reviews (0)