NoteGenNOTEGEN.

Sync

Sync Markdown, records, chats, and settings through Git, S3, or WebDAV.

NoteGen supports GitHub, Gitee, GitLab, Gitea, S3, and WebDAV. The selected provider becomes the primary sync method.

Sync configuration with GitHub repository, note, and record sync controls

What is synced

DataBehavior
Markdown and assetsFile-level upload, pull, delete, and delayed auto-sync after editing
Records, tags, chats, and settingsManual or automatic package upload/download with cross-device conflict detection

Device-specific values such as workspace paths and UI scale are excluded. Exclude Sensitive Settings also removes tokens, passwords, image-host settings, MCP settings, and other private values.

Provider setup

GitHub / Gitee / GitLab / Gitea

Enter a token and repository name. GitLab and Gitea support self-hosted instances. NoteGen can create a private repository on supported platforms when it does not exist.

ProviderMinimum permission for an existing repositoryAdditional permission to create one
GitHubFine-grained PAT with Contents read/writeAdministration read/write; replace it with a repository-scoped token afterward
Giteeuser_info, projectsSame
GitLabapiSame
Gitearead:user, write:repositorywrite:user, write:repository; older versions may expose only all

S3

Enter the access key ID, secret access key, region, bucket, endpoint, and optional path prefix. Compatible S3 object stores are supported. Save and test the connection before enabling automatic sync.

WebDAV

Enter the server URL, username, password, and optional path prefix. Synology, QNAP, Nextcloud, and other compatible servers can be used. HTTPS is recommended.

Note auto-sync

Disable it or choose a delay from 2 seconds to 2 minutes after editing stops. NoteGen can also pull when a file opens or when switching files. Auto-pull can overwrite the local version, so enable it only after validating your workflow.

Records and settings auto-sync

Changes enter an ordered upload queue. The first time it is enabled, choose Upload Local, Pull Remote, or Later. A new device normally pulls remote data; back up a device with unsynced local data before choosing.

Resolve conflicts

  • Merge both sides keeps new items from both sides, prefers the newer version of the same record, and merges settings under the current privacy rules.
  • Pull remote over local discards unsynced local changes.
  • Upload local over remote may discard changes from other devices.

Export a local ZIP from the title-bar sync menu before a high-risk overwrite.

Cross-device sync conflict choices on Android