← Back to Home

Advanced Usage

Command reference and configuration options for power users.

Commands

reMarkableSync sync

The default workflow — backs up your tablet and converts any updated notebooks to PDF.

reMarkableSync sync                    # USB connection
reMarkableSync sync --wifi             # Wi-Fi connection
reMarkableSync sync --cloud            # Read-only cloud connection
reMarkableSync sync --force-backup     # Re-download all files
reMarkableSync sync --force-convert    # Re-convert all notebooks
OptionDescription
--wifiUse Wi-Fi instead of USB
--wifi-host HOSTSpecify Wi-Fi IP/hostname (default: auto-discover)
--cloudUse the reMarkable Cloud API
--force-backupForce full backup, ignoring incremental state
--force-convertRe-convert all notebooks to PDF
--skip-templatesSkip backing up template files
--log-level LEVELSet verbosity: DBG, INF, WRN, ERR

reMarkableSync watch

Runs sync automatically on a schedule with a menu bar or system tray icon for status and control.

reMarkableSync watch                   # Default interval from config
reMarkableSync watch --interval 300    # Sync every 5 minutes

The status icon menu lets you:

reMarkableSync backup

Only download files from the tablet or cloud — no conversion.

reMarkableSync backup
reMarkableSync backup --wifi --force-backup
reMarkableSync backup --cloud --skip-templates

reMarkableSync convert

Only convert already-backed-up notebooks to PDF — no tablet connection needed.

reMarkableSync convert
reMarkableSync convert --force-convert

Full Pipeline

The pipeline command runs the complete flow: backup → PDF → AI OCR → Markdown export.

reMarkableSync pipeline \
  --output-dir ~/Documents/Notes \
  --ai-provider github
OptionDescription
--output-dir DIRRoot directory for Markdown output
--ai-providergithub (GitHub Copilot) or claude
--ai-model MODELOverride the default AI model
--skip-backupSkip the backup stage
--skip-convertSkip PDF conversion
--force-exportRe-export all notes even if unchanged
--notebook-filter PATTERNOnly process matching notebooks
--no-ai-ocrExport without AI transcription
--tags TAGSComma-separated tags for frontmatter

Logging & Debugging

All commands accept --log-level DBG for detailed output. A log file is also written to your backup directory's parent folder at remarkablesync.log.

reMarkableSync sync --log-level DBG

See How to get DEBUG logs for full details on log file locations.

Configuration

Settings are stored in <AppData>/remarkablesync/config.json. You can edit this file directly or re-run reMarkableSync config at any time.

Sensitive values (SSH password, cloud device token, AI API keys) are stored in your system keyring — never in the config file.

Cloud Setup

See Choosing a Connection Method for a detailed comparison of USB, Wi-Fi, and Cloud.

ModeAdvantagesLimitations
USBMost reliable direct connection; includes built-in templatesRequires a cable and SSH/developer access
Wi-FiNo cable required; includes built-in templatesRequires the same network and Wi-Fi SSH
Cloud APIWorks without the tablet nearbySlower, no system templates, and potentially incomplete without Connect

Cloud mode uses reMarkable's desktop-app API.

  1. Run reMarkableSync config and select Cloud.
  2. Open my.remarkable.com/device/desktop/connect.
  3. Sign in and create a code for a new desktop app.
  4. Enter the 8-character code in the wizard.
  5. The wizard verifies access and stores the resulting device token in your system keyring.
  6. Choose whether missing cloud files should be ignored or treated as deleted.
  7. Optionally wait for folder discovery and choose which cloud folders to sync.

The temporary pairing code is never stored. Later runs reuse the device token from the keyring.

Important: without a Connect subscription, files inactive for more than 50 days may stop appearing in the cloud until reopened on the tablet. Missing cloud entries are treated as unavailable, not deleted. Cloud sync only adds or updates local files and never removes an existing backup.

The wizard defaults to Ignore missing files. If you choose Treat as deleted, only files recorded by an earlier successful cloud sync are moved into a timestamped Cloud Archive directory. The operation is reversible and never permanently deletes local data.

Built-in system templates are not exposed by the cloud API and remain available only through USB or Wi-Fi device sync.

Custom OCR Instructions

You can customize how the AI transcribes your handwriting by providing a Markdown file with additional instructions. This is useful for:

Setup

Create a file at the default location:

# macOS/Linux
~/.config/remarkablesync/custom_instructions.md

# Windows
%APPDATA%\remarkablesync\custom_instructions.md

Or specify a custom path during reMarkableSync config when prompted for "Custom OCR instructions file".

Example

# Custom OCR Instructions

- I use "K8s" as shorthand for Kubernetes
- Convert "→" arrows to "->" in code contexts
- My handwritten "l" and "1" look similar - prefer letters in words
- Format any code snippets with proper markdown fencing

Pre/Post Sync Commands

You can run custom shell commands before and after each sync cycle. This is useful for:

Setup

Add these fields to your config.json:

{
  "pre_sync_command": "echo 'Starting sync...'",
  "post_sync_command": "cd ~/Notes && git add -A && git commit -m 'Auto-sync'"
}
FieldWhen it runs
pre_sync_commandBefore backup starts
post_sync_commandAfter all sync actions complete (backup, PDF, OCR)

Commands run in a shell (sh -c on macOS/Linux, cmd /c on Windows). If a pre-sync command fails, the sync continues. Post-sync command failures are logged but don't affect the sync result.