Logseq Git backup and sync on iPhone with LocalGit
Keep writing journals and pages in Logseq while LocalGit handles their GitHub history. This workflow applies to a file graph stored in a local folder that both apps can access under On My iPhone. Review changed files and tap Synchronize to commit, integrate, and push the graph’s non-ignored content.
How to use it
Check the graph type
Confirm you use a file graph and that its folder is visible under On My iPhone. Database graphs have a different layout.
Test with a copy
Keep a separate copy of your graph and test with a disposable graph and writable GitHub repository. Review setup choices before linking a nonempty folder; cloning can replace its active contents.
Make a test edit
Edit a journal or page in Logseq, let it finish writing, then review changes and synchronize in LocalGit. Confirm the file appears on GitHub. Assets and configuration are included unless Git ignore rules exclude them.
Keep the routine repeatable
Browse per-file Git history in LocalGit and use Apple Shortcuts to trigger Synchronize when Logseq opens or closes. Check the result; an automation trigger does not guarantee that every edit has reached GitHub.
Check the fit
Compatibility depends on the Logseq version and its folder access. Database graphs and hidden app storage are outside this file-folder workflow. iCloud Drive is unsupported. Synchronize is two-way Git sync and may change local files; keep a separate backup and avoid running another sync service on the same graph.
In short
Choose LocalGit for a compatible local Logseq file graph when you want journal and page history on GitHub through a guided Synchronize action. It offers stable capture, explicit conflict recovery, and Free per-file history. Choose Working Copy if you need its broader Git toolkit or automatic sync. Verify folder access with disposable notes first.
Product and platform references
