Auto-Export defines rules that automatically export reMarkable cloud documents to a local folder whenever they change - no manual Export click needed. Go to Settings > Automation > Auto-Export. Mac only.
Requires a Klass-RM Uploader Pro license. reMarkable Connect is never required.
Creating a rule
Each rule has:
- Source - a specific document, a folder (recursive by default), all documents, or documents carrying specific tags. You can also set exclusion tags to skip matched documents.
- Scope - the whole document every time it changes (the default), only the pages that changed since the rule's last export, or only pages carrying specific page tags.
- Formats - any combination of PDF, PNG, SVG, Markdown, and Highlights, exported together every time the rule fires.
- Retention - keep everything (the default), only the latest, the last N, or N days' worth.
- Filename template - built from tokens like
{name},{date},{time},{datetime},{n},{hash},{pages},{format},{folder}, and{path}. Default is{name}_{datetime}. - Replicate cloud folder structure - optional toggle to mirror the document's reMarkable folder hierarchy under the destination instead of writing everything flat.
If a new rule already matches more than 10 documents when you save it, you are prompted to either export everything right away or only export future changes.
Using tags in a rule
Tag and exclusion-tag fields have a searchable "Browse tags..." popover alongside free-text entry, so you can browse a large account's tag vocabulary instead of typing blind.
The app also proactively looks up tags in the background for every document, not just ones you have opened or exported before - a toggle next to "Look up all tags" controls this (on by default). Tag lookup itself is free for everyone and only requires a paired account - only the auto-export rules that consume those tags are Pro.
Skipping empty files
Same toggle as manual export - Skip files with no typed text or highlights, for Markdown/Highlights formats only. Pre-checked by default for a brand-new rule. A matched document that produces nothing under a rule's formats still counts as up to date (it will not be retried every time your account changes), but is logged as skipped rather than exported.
Activity log
Each rule has an activity log explaining every non-export outcome - unchanged, no matching pages, excluded by tag, capped this run, and so on. The cloud browser's inspector also shows which rules cover the currently selected document or folder, and why.
A behavior to know about
Under the default whole-document scope, a metadata-only change - a rename, a pin, or a move with no content edit - still produces a byte-identical re-export, since it bumps the document's version marker the same way a real content edit does. If this bothers you, switch the rule to "only changed pages."
How it detects changes
Auto-export reuses the same account-change signal the cloud file browser's auto-refresh uses - there is no separate polling - and reuses the same persistent Export Queue described on the Exporting Files from reMarkable page to actually render and write each job. Auto-export is purely a rules layer on top of both.