Use this guide before clearing settings, changing machines, or collecting support data.
What to back up
Back up the local application data location for the operating system before a destructive reset. The location is build- and OS-dependent, so confirm the path shown by the current build or its diagnostic bundle before copying files.
Keep separate copies of:
- saved article metadata and collections;
- local PDFs and PDF cache content;
- annotations and Writer projects;
- local AI model files;
- configuration and settings;
- logs and MCP activity logs;
- exported diagnostic bundles.
Do not assume that a cloud account contains local PDFs, annotations, or local models. Sync boundaries are described in Sync & Cloud.
Safe actions first
1. Export logs or a diagnostic bundle. 2. Clear a visible UI state or one cache only. 3. Reset one AI setting when the issue is limited to AI configuration. 4. Reset the WebEngine profile only when browser state is the suspected cause. 5. Copy local data before any full reset.
Destructive reset
Deleting the complete application data directory can remove settings, caches, local indexes, annotations, saved metadata, and other local state. Treat it as a last resort. Make and verify a backup first.
Restore
Restore only the data category needed for the issue. Do not overwrite a newly created configuration until the application is closed and the backup is verified. If restore behavior is unclear, keep the original copy and contact Support.