Repository navigation
FAQ
Short answers. The official FAQ has the longer versions.
No. The editor works immediately with notes stored in your browser. Connecting GitHub gives you a backup and sync across devices.
In two places: IndexedDB in your browser, and .md files in your GitHub repository. Nowhere else.
Yes, permanently. Your notes live in your own GitHub account, so there is no storage cost to pass on.
Yes, under the Apache 2.0 license.
repo is the narrowest classic GitHub OAuth scope that can write to a private repository. Nothing about your profile, email, organisations or gists is requested. If you only keep public notes, choose Public repositories only when signing in.
Yes: any repository you can write to, on any branch, optionally limited to one folder.
Yes. Edit them on github.com, in VS Code, in Obsidian, or from the command line. ForkLeaf picks up the changes on its next sync.
No. Consecutive edits to a note are combined into one commit.
Fully. Writing, diagrams and exports all work without a network. Changes queue up and are pushed when you reconnect.
ForkLeaf detects the conflict and asks which version to keep. It never silently merges.
Flowcharts, sequence, class, state and ER diagrams, Gantt charts, mind maps, pie charts, user journeys, timelines, git graphs and quadrant charts.
Not a native one, but the web app works in a phone browser. The editor is designed desktop-first.
No. There is no ForkLeaf database. Note content only passes through the API proxy on its way to GitHub.
Delete the repository on GitHub, clear the site data in your browser, and revoke the ForkLeaf OAuth app in your GitHub settings.
Still stuck? Ask in Q&A or email support@forkleaf.in.
Using ForkLeaf
Project