Docs / Windows Performance
Windows Performance Guide
If Bookshaper feels slow on Windows — long project-open times, lag when saving, the app hanging briefly before loading a recent project — the cause is almost always something environmental outside of Bookshaper itself. This guide walks through the common causes in the order you should check them.
1. Is your project inside OneDrive? (most common cause)
By default on Windows 10/11 with a Microsoft account, your Desktop, Documents, and Pictures folders are silently redirected into OneDrive. The folder names stay the same in File Explorer's sidebar, so you might not realize that saving a project to “Desktop” actually puts it in a cloud-synced folder.
When a file-heavy application like Bookshaper operates on a OneDrive-synced folder, every single read and write is intercepted by OneDrive's sync filter driver. On a 150-scene project this can make open and save operations 10× slower or worse.
3. Third-party antivirus (Norton, Kaspersky, McAfee, Bitdefender, etc.)
If your PC was set up with a third-party antivirus instead of (or in addition to) Windows Defender, the same exclusion-list concept applies but the location differs per vendor. Common paths:
- Norton: Settings → Antivirus → Scans and Risks → Exclusions/Low Risks
- Kaspersky: Settings → Threats and Exclusions → Manage exclusions
- McAfee: My Protection → Real-Time Scanning → Excluded Files
- Bitdefender: Protection → Antivirus → Settings → Manage Exceptions
Add your Bookshaper projects folder as an exclusion. Vendor documentation is authoritative; the list above is just a starting point.
How to tell if your symptoms are environmental or a Bookshaper bug
Bookshaper emits detailed per-phase timings on every project open at <project-dir>\reference\load-timings.json. A few signatures distinguish environmental from in-app slowness: