READ-ONLY APPLE PHOTOS MIGRATION PREFLIGHT

Know what will
make the move.

Inventory readable local originals, explicit referenced gaps, iCloud-only candidates and unknown evidence before you migrate an Apple Photos library.

See the $29 launch plan Review the evidence classes

Local processing
SQLite snapshot · read-only
No forced downloads

CAPTURED FROM THE CURRENT RELEASE BUILDFICTIONAL FIXTURE

LibraryProof Release build showing a fictional Photos library audit with source details, evidence classifications and a selected missing reference

The interface is real. The visible filenames, paths and counts come from LibraryProof’s explicit fictional marketing fixture.

AUDIT / 7F3C1B8EObservable evidence stays separated.

214: Local
18: Referenced
3: Missing
42: Cloud candidates
7: Unknown

CAPTURED FROM THE CURRENT RELEASE BUILD

Inside the actual app.

RELEASE / UNIVERSAL2

This is the working macOS interface, photographed with the app’s opt-in fictional fixture. The UI is real; the library name, paths and counts are sample evidence.

LibraryProof Release build crop showing the fictional selected Photos library, audit identifier, record count and read-only snapshot mode — SOURCELibrary context stays pinned
The selected package, audit ID, record count and read-only database mode stay explicit throughout review.

LibraryProof Release build crop showing filters and fictional rows for missing, iCloud candidate, unknown and referenced evidence — REVIEWAvailability states stay separate
Missing references, cloud candidates and unknown evidence never collapse into one reassuring count.

LibraryProof Release build crop showing the evidence inspector for a fictional missing referenced file with observed path and classification reason — INSPECTOREvery label carries a reason
The inspector preserves the observed path, readable-byte state and bounded reason behind each classification.

THE EVIDENCE TAXONOMY

Five states.
No convenient guessing.

Migration risk hides when every unmatched record is called “missing.” LibraryProof keeps locally proven bytes, external references, cloud clues and unsupported evidence in distinct lanes.

01 / LOCAL

SHAREADABLE

Locally available

A supported regular media file is readable and SHA-256 hashed. Only proven bytes enter the local export estimate.

02 / REFERENCE

EXTPRESENT

Referenced · present

An explicit path or symbolic link resolves to a readable regular file, with its own byte count and hash.

03 / GAP

404PATH

Referenced · missing

An explicit reference exists, but no regular file is present there. The absent path remains actionable evidence.

04 / CLOUD CLUE

☁CANDIDATE

iCloud-only candidate

A cloud identifier exists without readable local bytes. It is never promoted to a confirmed missing original.

05 / HOLD

?UNKNOWN

Unknown

Unsupported schema or ambiguous evidence stays unresolved, visible and excluded from completeness claims.

THE ARCHIVAL WORKFLOW

Inspect. Separate. Reverify. Receipt.

01
Choose one source
Select a .photoslibrary package or Photos export folder. The normal first launch contains no demo data and nothing scans without your choice.
02
Snapshot the database privately
Observable database files are copied to a temporary area, then opened with SQLite read-only. The selected package is never opened for writing.
03
Review every unresolved lane
Filter missing references, cloud candidates and unknown records. The remediation checklist is derived from those visible gaps.
04
Publish portable evidence
LibraryProof reverifies observable source metadata and hashes before atomically creating JSON, CSV, Markdown and checksum artifacts.

A BOUNDED ESTIMATE

Count bytes you can read.
Exclude everything else.

LibraryProof’s export estimate is deliberately smaller than a promise of library completeness. A file contributes only when its local bytes are readable and hashed.

LOCAL EXPORT ESTIMATEOBSERVED

232 files84.6 GB

+ local originals
+ referenced and present

− missing references
− cloud candidates
− unreadable / unknown

NOT A COMPLETENESS CLAIM

THE TRUTH BOUNDARY

It does not repair Photos.

No Photos database writes
No library merge or cleanup
No iCloud credentials
No forced media downloads
No “missing” label for cloud uncertainty
No supported-schema claim without evidence

LIBRARYPROOF / PORTABLE HANDOFF

library-audit.jsonlibrary-audit.csvlibrary-audit-receipt.mdexport-receipt.jsonMANIFEST.sha256

THE RECEIPT

Evidence another person can review.

The package records classifications, reasons, observable paths, byte counts and SHA-256 values without depending on the original app session.

Deterministic content for the same audit and export time
CSV formula prefixes neutralized for spreadsheet review
New destination folder with no partial publish on cancellation

MIGRATION FIELD NOTES

Read the evidence before moving the archive.

NOTE 01

How to audit an Apple Photos library before moving it

A read-only checklist for local originals, referenced files, cloud candidates and unknown records before an Apple Photos library migration.

Read guide →NOTE 02

Referenced files vs iCloud originals in Photos on Mac

Understand why referenced-missing files, iCloud-only candidates and unknown Photos records must remain separate during migration planning.

Read guide →NOTE 03

Apple Photos library migration checklist for Mac

Plan an Apple Photos library move with source backups, read-only evidence, local-byte estimates, gap review and post-copy verification.

Read guide →

QUESTIONS, ANSWERED

LibraryProof FAQ

Does LibraryProof repair my Photos library?+

No. It is a read-only migration preflight. It does not write the Photos database, merge libraries, repair a package or change media.

Can it prove every iCloud original is available?+

No. A cloud-associated record without readable local bytes is labeled an iCloud-only candidate, not a confirmed missing file and not a verified remote original.

What counts toward the export estimate?+

Only locally readable regular files with a computed SHA-256 hash. Missing references, unreadable files, cloud candidates and unknown records are excluded.

What happens with an unsupported Photos schema?+

The schema and affected evidence remain unknown. LibraryProof does not infer compatibility or present an unsupported database as complete.

Can I inspect an exported Photos folder?+

Yes. LibraryProof can inventory supported media in a selected export folder, but it clearly reports that a folder scan cannot prove the source library was completely exported.

What does the evidence package contain?+

A deterministic JSON audit, reviewable CSV, Markdown receipt, export receipt and MANIFEST.sha256 checksum list in a new destination folder.

How much will LibraryProof cost?+

The planned price is US$29 as a one-time purchase for one Mac. Checkout remains closed until signing, notarization and representative real-library validation are complete.

LIBRARYPROOF FOR MACOS