Troubleshooting

Protect the current copy first

If the writing is still visible, keep the app open. Export a World copy before signing out, clearing site data, reinstalling, deleting a World, or importing over the same working location. If an export fails, keep the original and record the error.

In particular, clearing browser data is not a harmless reset for local-only Worlds. It can erase the only copy of the writing.

I can’t find my World

1. Clear the library search and choose All Worlds, then check the intended Workspace. The browser’s Worlds list has no Local entry; existing browser-local Worlds remain in All Worlds. Desktop also offers Local. Check whether you are viewing another book inside the same World.
2. For browser-local work, return to the original browser, profile, and device. A different browser does not share its storage.
3. For synced work, check the signed-in account, Workspace membership, connection, and pending/error state.
4. For desktop files, locate the original folder and use Open folder. For erased local-only browser data, use an external backup; signing in alone cannot recreate it.

I can read but not edit

In the browser, first check that you have both a purchased license and a sync subscription. For desktop writing, check the trial/license state in Settings → Account. Then check the Workspace content grant: Read only or No access cannot be fixed by buying another device seat. A disabled live or version action can also reflect a collaboration constraint.

Continue read-only only dismisses the access dialog; it does not enable New World, imports, typing, or changes to records and planning. Use Set up sync for browser access, or Your account → Desktop app to download the desktop app and use a trial or license without sync. Download existing browser-local Worlds separately before transferring them.

Export remains available for locally readable work. Reconnect and let account status refresh after purchase; dismissing a notice or signing in alone does not establish both entitlements. Do not sign out, delete the World, or make a duplicate purchase to troubleshoot access.

Saving or sync needs attention

1. Keep the error visible and note what action caused it. Save and sync are related but distinct: a local write and a remote upload can fail separately.
2. Check connectivity for remote operations and available device/browser storage for local ones. Do not clear app storage to free space while it contains the only copy.
3. Retry through the offered control when the cause is resolved. Watch for pending work to complete before moving devices.
4. If it still fails, export what you can and contact support. Avoid repeatedly importing the same file to try to force a sync merge.

An export, image, or import is incomplete

Read the report for skipped or unreadable files. Keep the original World and media folder intact. When moving a ZIP export, extract it with the media in its original relative locations; opening project.plotscribe alone can omit the accompanying images.

For imported manuscripts, compare the preview and original source. Complex formatting may be outside the supported conversion. For compile results, verify the selected book, inclusion flags, sample size, and output destination before assuming text was lost.

Ask for help safely

Contact support@plotscribe.app with the browser or desktop version, operating system, steps to reproduce, and the exact error text. Say whether the World is local-only, file-backed, or synced, and whether you have a separate backup.

Do not send passwords, sign-in links, tokens, or your full manuscript by default. Start with a redacted screenshot or a minimal example you are comfortable sharing.