You open Scrivener to carry on with your book, dissertation or script and the project will not open, opens empty, or is missing chapters you know you wrote. Sometimes Scrivener reports that the project is already open elsewhere; sometimes the whole project has vanished from the folder you kept it in. Before you try anything else, take a breath: Scrivener keeps more copies of your work than most people realise, and the first few things you do decide whether those copies survive.
First: stop saving over things
Do not create a new project with the same name in the same place, do not “tidy up” the folder, and do not let a sync service overwrite the project from another computer until you know which copy is good. If you can see the project at all, copy the whole project (the folder or package ending .scriv) to another drive or a different folder before experimenting. Work on that copy, never the original.
How a Scrivener project is stored
A Scrivener project is not a single file. The .scriv item is a folder (on a Mac it is shown as a package, so it looks like one file) containing a project file plus a set of subfolders holding each document in your Binder as a separate file. This matters for two reasons:
- If only part of that folder is damaged or out of date, Scrivener may open the project but show blank or missing documents, because the index and the text files no longer match.
- Copying, zipping or syncing only part of the folder (for example, a sync that stopped half way) produces exactly this kind of “missing chapters” problem.
Look for Scrivener’s automatic backups
By default, Scrivener makes an automatic backup of a project when you close it, and keeps a number of the most recent ones. These are complete copies of the project, usually stored as zip files with “bak” and a number in the name. To find them:
- Open Scrivener’s settings: Scrivener > Settings (or Preferences) on a Mac, File > Options on Windows, and go to the Backup section.
- Note the backup folder location shown there, and whether backups are compressed and how many are kept.
- Open that folder and sort by date. Find the most recent backup from before the problem started.
- Copy the zip to your desktop, unzip it, and rename the resulting project so it cannot be confused with the original (for example, add “restored” and the date).
- Open the renamed copy and check the chapters you are worried about before doing anything else.
If you write in more than one place, check the Backup settings on every computer you use; each one keeps its own backups.
Snapshots and other places your text may be
- Snapshots: if you took snapshots of a document before rewriting it, older versions are stored inside the project and can be viewed from the Inspector.
- Compiled output: any Word, PDF or ePub file you compiled and sent to an editor or supervisor contains the text as it was at that point.
- Emails and cloud folders: drafts sent to yourself or others, or exported copies in OneDrive, Google Drive or iCloud Drive.
- Your own backups: Time Machine on a Mac or File History on Windows can bring back an older copy of the whole .scriv folder.
Dropbox, sync and two computers
Many writers keep projects in Dropbox so they can work on a laptop and a desktop, or with Scrivener on iPad. This works well when one device finishes syncing before the other opens the project. Problems usually come from opening the same project on two machines at once, or closing a laptop before syncing has finished. Signs include a warning that the project is open on another computer, or “conflicted copy” files inside the project folder.
- Close Scrivener on every device and let the sync service finish completely.
- Check the sync service’s own version history or deleted files for the project folder; Dropbox, OneDrive and Google Drive all keep earlier versions for a period depending on your plan.
- Do not delete conflicted copies until you have opened a copy of the project and confirmed your text is there.
When the drive itself has failed
If the project is missing because the laptop will not start, the external drive is not recognised, or the drive is clicking, slow or showing errors, the problem is the storage rather than Scrivener. In that case:
- Switch the computer or drive off and leave it off. A failing hard drive can get worse with every attempt to read it.
- Do not run disk repair tools or free recovery software on it, and do not reinstall the operating system onto it.
- Check the backup and sync locations above from a different computer first; you may already have a recent copy.
If no usable copy exists, a recovery lab can work on the drive itself. Because a .scriv project is a folder of many small files, getting the whole folder back intact is what matters, and that is far more likely if the drive has not been worked hard after it started failing. You can read more about our laptop data recovery and hard drive data recovery in London.
Preventing it next time
- Leave automatic backups switched on, and consider pointing them at a different drive or a cloud folder from the one the project lives in.
- Increase the number of backups Scrivener keeps if you work on one long project for months.
- Use File > Back Up to make a dated backup at milestones, such as finishing a draft.
- Only open a synced project on one device at a time.
Talk to Data Doctor
If your Scrivener project was on a laptop or drive that has failed and there is no backup to fall back on, call Data Doctor on 020 7394 2529 for a free initial consultation. Our clean room lab is at Unit 1 The Willows, 80 Willow Walk, London SE1 5SY.