Skip to content

Damaged and missing files

Frameleaf checks every file each night. When a photo’s file is damaged, or has gone missing from the drive, Frameleaf tries to fix it by itself straight away: it repairs damaged photos, looks for an exact copy of missing ones, brings the original back from Cloud Backup, and asks your phones for it. Damaged and missing files lists every file Frameleaf found a problem with, what it did about it, and anything left for you.

Nothing is deleted to fix a file. A repaired photo takes the damaged one’s place in your library, and the damaged file is kept beside it, so any fix can be undone.

Open Library Care, then Damaged and missing files. Every account has it: you see your own files, and an administrator also sees the rest of the household’s. You can also get there from:

  • Things to fix: Review on Missing files or Damaged files, and, for administrators, on Fixed for you.
  • Library health, if you aren’t an administrator: when one of your files is missing or damaged, its row opens this page.
  • File checks, for administrators: See damaged and missing files, under When a check finds a problem.
  • The Overview, for administrators: see On the Overview.
  • The photo itself: see In the photo viewer.

Frameleaf calls a file damaged only when it has proof:

  • The file has changed since Frameleaf stored it, for example because part of a drive is failing.
  • The file is blank or empty.
  • The file can’t be opened at all.
  • Part of it is missing: a JPEG that stops partway through the picture, or a video that ends well before its stated length.

A file that opens, and hasn’t changed since you added it, is not damaged. That includes:

  • Old or unusual photos that a strict reader complains about, such as a JPEG with a missing end marker or odd details, when the whole picture is there. Frameleaf opens them the way other photo apps do and leaves the file alone.
  • Files Frameleaf can’t show yet. A RAW file, cinema RAW video, design file or font that no reader can draw is kept as it is. See Supported formats.
  • Very large videos. A video is checked by reading through the whole file, with no time limit while the read keeps moving. A 20 GB or 50 GB video is never called damaged because checking it took a long time.
  • Files that couldn’t be checked, because the drive was busy or stopped responding, or the server was short of memory. These show Couldn’t be checked, don’t count as damaged, and are tried again at the next file check.

If an earlier version of Frameleaf listed a large video or an old photo as damaged, the next nightly file check clears it. If an old JPEG was repaired when its picture was complete, Undo repair puts your original file back.

Frameleaf starts as soon as a problem is found, for example when a photo’s preview can’t be made, and again after each night’s file checks. Every step it takes is written into the file’s history.

If many files go missing at once because a drive isn’t plugged in, Frameleaf waits for the drive instead of treating the photos as lost.

  1. It checks the file to find out what’s wrong, in plain words: the file stops partway through the picture, there’s data in front of the picture it doesn’t recognise, the file’s details are damaged, the file is blank, or it can’t be read.
  2. It looks for the original, but only when the file has changed since Frameleaf stored it, for example because part of a drive is failing. An exact copy on this server’s drives is put back, or the original is restored from Cloud Backup, and the changed file is kept beside it. A real original always comes before a repair.
  3. It repairs the photo, when Repair damaged photos by themselves is on (it is unless your administrator turned it off). The damaged file is kept beside the repaired one, in Library care, and Undo repair puts it back.
What was wrong What the repair does
The file stops partway through the picture Rebuilds the picture from the part that was there, and copies the date, place and camera details over
Unreadable data in front of the picture Removes it. Nothing in the picture changes
The file’s details are damaged Rebuilds the details. Nothing in the picture changes, and the date and place are copied over
Damaged data around the picture Fixes it. Nothing in the picture changes
Another kind of image saved with a .jpg name Saves it as a real JPEG
Only the small preview inside the file can be read Saves that preview. The full picture was lost

Repairs work on JPEG photos. When the date, place or camera details can’t all be copied over, the history says so.

With Repair damaged photos by themselves off, damaged photos wait in Needs you with Repair…, where you see the repair before choosing it.

When the end of a file was cut off before it came to Frameleaf, the repair saves the part that was there, and the rest of the picture is grey. The file shows Part saved, with a line such as “The end of the file was cut off. 72% of the picture was saved.” Its history explains that the bottom of the picture couldn’t be saved, and that Undo puts the damaged file back as it was. A repair that could only save the small preview inside the file is Part saved too.

Part saved photos are listed first in Fixed for you, so you can look at them before anything else.

  • Blank: “Every part of it is blank. The picture was lost before it came to Frameleaf, so no copy of it was ever stored.”
  • A photo that was already damaged when it arrived. Any copy of it has the same damage, so Frameleaf doesn’t look for one.
  • Other kinds of photo, such as PNG or HEIC, that can’t be read.

These wait in Needs you as Can’t be repaired.

A file that couldn’t be read after three tries, for example because its drive was busy, isn’t called damaged. It shows Couldn’t be checked, and Frameleaf tries again at the next file check.

A file Frameleaf can’t make a preview of yet, such as cinema RAW video, a RAW file from a camera its decoders don’t know, or a design file with no picture inside it, isn’t damaged either: “It’s fine and kept as it is, but Frameleaf can’t make a preview of it.” It goes to Left as they are.

The photo is still in your library and shows its small preview, but its original isn’t on the drive.

  1. For a photo that came from another app, it looks where that app was moving it. Some apps, such as Immich, lost files while sorting them into folders. When the app’s own records say where it was moving a file, Frameleaf looks in that exact spot first.
  2. It looks for an exact copy. Frameleaf compares every file on this server’s drives, and in the folders your old photo app used, by its contents, not its name. A copy that was renamed or moved to another folder is still found. A copy already in your library is used where it is: “Nothing was copied, moved or renamed.” A copy in your old photo app’s folders is copied into your library, and the old one is left where it was.
  3. It checks your backups. If Cloud Backup has the original, it’s restored where it was. It’s checked against the photo and never replaces anything. If your Cloud Backup began after the file was already lost, the history says so.
  4. It asks your phones. See Phones send lost photos back.
  5. It asks iCloud Photos, for a photo that came from iCloud Photos, when copies and Cloud Backup have nothing. The history says Asked iCloud Photos, Waiting: Frameleaf gets it straight away, or the next time it syncs if your connection only syncs when you ask. Then it says Found (“iCloud Photos had the original. Your library uses it now.”) or Not in iCloud.

If none of these finds it, the photo waits in Needs you.

Only an exact copy is ever used by itself. A file with the same name, date or picture is never put in its place.

A good copy that arrives later is put in the lost or damaged file’s place, instead of being skipped as already in your library. That’s true however it arrives: uploaded on the web, backed up from a phone or from Frameleaf Desktop, saved with the browser extension, or brought in by an import, such as Google Photos, iCloud Photos or a preservation package.

  • For a missing photo, the copy becomes its original again.
  • For a damaged photo, the copy takes the damaged file’s place, the damaged file is kept beside it, and Undo puts it back. The history says a phone sent it, when one did.
  • If what you upload is the very same damaged file, nothing is replaced.

“Phones with the Frameleaf app look for photos this server has lost each time the app is opened, and send back any they still have. Nothing to tap.”

  • Each time the iPhone or Android app is opened and signed in, it gets the list of your photos whose original is missing, looks through the photos on the phone, and sends back any it still has with your normal backup. It uses the networks you allow for backup.
  • A phone only ever gets its own account’s list.
  • While Frameleaf waits, the photo shows Waiting for a phone: “Your phones send it back if they still have it, the next time Frameleaf is opened on them.” It still counts in Needs you, and you can act on it.
  • Each phone that looked adds a line to the history, such as Checked on iPhone, Not there. When a phone has the photo, the history says it sent it back, and Put it back: “Your library uses the photo your phone sent.”
  • Once every phone used with this library has looked, the history says Not on a phone.

If you have an old phone in a drawer that used Frameleaf, charge it and open the app.

Administrators can turn this off with Ask phones for missing photos. See The settings.

The top of the page says how things stand:

  • Every file is there and opens: “Frameleaf checks every file each night. If one goes missing or gets damaged, it tries to fix it by itself and lists it here.”
  • Nothing needs you, with how many files Frameleaf fixed by itself.
  • How many files need you, such as 3 files need you, with how many Frameleaf found and how many it fixed by itself.

Then Show chooses one of three lists:

List What’s in it
Needs you “Frameleaf has tried everything it can for these. Each one says what it tried and what you can do.” When it’s empty: “Nothing needs you. Anything Frameleaf can’t fix by itself waits here.”
Fixed for you “Repaired, or found again somewhere else on this server. Open one to see what changed, or to undo it.”
Left as they are “Files Frameleaf can’t show yet, and ones you chose to keep as they are. They are safe and still backed up.”

Each row shows the picture (the small preview, for a missing photo), the file’s name, a one-line story, whose library it’s in and when, and What happened. The label on the row is one of:

Label What it means
Repaired A damaged photo was repaired. The damaged file is kept
Part saved Repaired, but part of the picture couldn’t be saved
Found again An exact copy was found, or the original came back from Cloud Backup or a phone
Waiting for a phone Frameleaf is waiting for your phones to look
Needs you Frameleaf has tried everything it can
Left as it is Kept as it is, by you or because Frameleaf can’t show it yet

Long lists show the first files, then Show N more.

Select What happened on a row to open the file’s history. It shows:

  • The picture. For a repair, the damaged file (Won’t open) is shown beside the repaired photo. Otherwise, the small preview Frameleaf still has.
  • Now, such as Repaired, Repaired, part saved, Found again, Missing, Waiting for a phone, Can’t be repaired, Couldn’t be checked or Left as it is; Taken, the photo’s date; and Library, whose library it’s in.
  • The step-by-step history, in plain words. For example, a photo that came from Immich might read Brought into Frameleaf, Missing; Looked where Immich was moving it, Not there; Looked for an exact copy, None found; Checked your backups, Found; Restored it from Cloud Backup, Restored.

The buttons depend on how things stand:

The file is Buttons
Repaired or Part saved Undo repair, Download damaged file, Keep repaired photo
Found again Undo, Done
Missing or Waiting for a phone Remove from library…, Look in a folder…
Needs you, damaged Remove from library… and Keep as it is, with Repair… when a repair is possible but wasn’t made by itself (repairs were off, or you undid one), or Look in a folder… when the file changed after Frameleaf stored it
Couldn’t be checked Remove from library…, Keep as it is, Try again
Left as it is Done
  • Undo repair puts the damaged file back as it was. Frameleaf won’t repair that photo again unless you ask, so it moves to Needs you with Repair….
  • Undo on a photo that was found again lists it as missing again, or puts the changed file back. The file that was found isn’t deleted.
  • Download damaged file saves the kept damaged file, for example to try another repair tool.
  • Repair… shows the repair, before and after, so you can choose it.
  • Look in a folder… searches one folder for an exact copy. See below.
  • Keep as it is moves the file to Left as they are. It can still be downloaded, shared and backed up.
  • Remove from library… asks first, then moves the photo to the trash. For a missing photo, its small preview goes with it.
  • Try again asks Frameleaf to go through its steps again. What it finds shows in the history.

Only the photo’s owner can use these. On someone else’s file, an administrator can only use Try again, and only while the file needs someone.

When a photo is in Locked and Locked encryption is on, the files Library care keeps for it are encrypted with it: the damaged file kept after a repair, and a file moved aside when you undo a restore. When the photo leaves Locked, they’re opened again with it. Photos that were already in Locked are covered by themselves. There’s nothing for you to do.

If a kept file’s drive was away when the photo left Locked, the file stays encrypted until Frameleaf opens it later, the next time your key is open. Until then, a kept file that is still encrypted is never handed out or put back:

  • Download damaged file says “The damaged file Frameleaf kept can’t be opened yet. Frameleaf will try again; try later.”
  • Undo says “A file Frameleaf kept for this photo can’t be opened yet, so this fix can’t be undone now. Frameleaf will try again; try later.”
  1. Check the drive first. “Missing” doesn’t always mean gone. If a drive is unplugged, a share isn’t connected or a folder was moved, put it back and the next file check clears the list by itself.
  2. Open Frameleaf on your phones, including old ones. Each one sends back any lost photo it still has.
  3. Look in a folder. A USB drive, a memory card or an old computer’s disk may still have the photo. Select Look in a folder…, choose the folder, then Look in this folder. “Frameleaf compares files by their contents, so names don’t matter.” The list shows only folders this server can already see: your own library folders and the folders of photos you own, and for administrators, recovery folders and drives added in Frameleaf Manager. To look on another drive, connect it to the server and add it in Frameleaf Manager first. The dialog links there for administrators, and tells everyone else to ask whoever runs the server.
  4. If it’s gone for good, keep the small preview by leaving the photo where it is, or select Remove from library….
  • Repaired or Part saved: open What happened and look at the photo. If you’re happy, select Keep repaired photo. If not, Undo repair puts the damaged file back, and Download damaged file gives you a copy to try elsewhere.
  • Can’t be repaired: if you have the photo somewhere else, such as on a phone, an old computer or a memory card, use Look in a folder… when it’s offered, or upload it again: a good copy takes the damaged file’s place. See Uploading or importing the photo again. Otherwise choose Keep as it is or Remove from library….
  • Couldn’t be checked: select Try again. If it keeps happening, check the drive.

A photo with a problem that still needs someone shows a flag at the top of the viewer, beside its name:

  • Original missing: “Only a preview of this photo is left. See what Frameleaf tried and what you can do.”
  • Damaged file: “This photo’s file is damaged and couldn’t be repaired. See what Frameleaf tried and what you can do.”

Select the flag to open the photo’s What happened. On a phone, the flag shows only its icon. Photos that were fixed, including Part saved ones, photos left as they are, and files that couldn’t be checked show no flag.

When the original is missing, Download, Download original, Edit, Send a copy and exporting a still don’t fail. A notice says “Only a preview of this photo is left.”, with See what happened.

Administrators see damaged and missing files on the Command Center’s Overview:

  • Your files (“Every original is there and opens”) says All there or how many are missing, and how many were fixed.
  • Done for you: “Frameleaf fixed N photos last night”, today or this week. “They wouldn’t open or had gone missing. Every damaged file is kept, so any fix can be undone.” Review what changed opens Fixed for you, and Dismiss hides the row until a newer fix lands. It shows for a week.
  • When photos are missing or can’t be repaired, a When you can item says how many, with See what you can do.

In Background work, a failed item for a photo with a file problem shows In Library care, which opens that photo’s history. When nightly processing or another piece of work leaves photos over because their original is missing or their file is damaged, Review what failed in Recent work has Open in Library care, which opens this page. See When some photos are left over.

Administrators find What Frameleaf does by itself on this page: “As soon as a problem is found, and after each night’s file checks.”

Setting Default What it does
Repair damaged photos by themselves On “A repaired copy takes the damaged one’s place, and the damaged file is kept beside it. Any repair can be undone.” Off: damaged photos wait in Needs you
Look for missing files Always Compares files on this server’s drives, in the folders your old photo app used and in your backups by their contents. It can’t be turned off
Ask phones for missing photos On Phones look for lost photos each time the Frameleaf app is opened, and send back any they still have

Repair damaged photos by themselves and Look for missing files are also in File checks, under When a check finds a problem. See Library care settings.

Below the settings, the page makes a promise: Nothing is deleted to fix a file. “A repaired photo takes the damaged one’s place in your library, and the damaged file is kept beside it. When Frameleaf moves a file into its folder, the old one stays until the new copy has been checked to match it exactly.” See How files are moved.

  • You see your own damaged and missing files, and can undo, repair, replace or remove them.
  • An administrator also sees the household’s files, with the owner’s name, the state and the history, but not the picture. In its place is a note such as “Only Sam sees this photo and can undo or replace it.” They can only use Try again on someone else’s file.
  • Partners and shared links see none of this.
  • A photo in your Locked folder can’t be undone from here, and its damaged file can’t be downloaded. With Locked encryption on, the files kept for it are encrypted too. See Photos in Locked.

When you import a library from another app, such as Immich, the import records what it knows about each photo whose file wasn’t there. Its history starts with Brought into Frameleaf, Missing: “Immich listed this photo, but its file wasn’t there. Only its small preview came across.” Frameleaf then looks in the folders the import used, and where the old app’s records say it was moving the file, as well as everywhere else it can look. A copy found in the old app’s folders is copied into your library; the old one is left where it was.