Verify a Vault export in your browser
No verifier installation is needed. This guide checks a matching export pair in the hosted application, then shows how to download a readable copy if you want one.
Before you begin
You need the completed .pfv package and matching
.key.json. Already received them? Start below. Otherwise,
export one file from Desktop.
The package limit is 256 MiB, including the export container. For larger packages, use the native Linux reader. Launching the browser locally does not remove this limit.
Keep the key file private. Anyone with the package
and its .key.json can decrypt that revision, even after
their PhotonFile access is revoked. Treat a decrypted copy as
sensitive too.
Selecting files does not upload them. Processing runs in this tab after the application is ready. The hosted application still relies on the live website and your browser; understand that trust boundary before selecting sensitive data.
1. Open the verifier and wait for readiness
In the application, find the Result section. Wait for Ready for local input. The buttons remain disabled while cryptography initializes. The verifier opens in a new tab so you can keep this guide visible while following the steps.
Expected result: the readiness message appears and processing controls become available.
2. Select the matching files
-
Under Verify a Vault export, choose your
.pfvin Encrypted package (.pfv). -
Choose its matching
.key.jsonin Secret key (.key.json).
Expected result: both file selectors show the files you intended. You do not need the advanced Full test packages and published vectors section.
3. Verify content and layout
Select Verify content and layout, then wait for the result.
Expected result: Content and layout verified. The report below records the checks and their limitations. No readable file is downloaded at this step.
If verification fails, stop. Confirm the two files belong to the same completed export. Do not edit the key or package to make a check pass.
4. Optionally decrypt a readable copy
After successful verification, select Decrypt verified content. The application rechecks the verified pair and starts a download. Save the result privately using your browser's download controls.
Expected result: a decrypted copy is available in your browser's downloads. This does not modify the original export. If you replace either selected input, verify the new pair again before decrypting.
5. Save a report and finish
Optionally choose Download JSON or Download HTML in the Result section. A report records what was checked. It is not a digital signature from the file's author.
Select Reset or close the tab when finished. Reset clears the selected inputs and retained verification state. It does not delete exported files, saved reports, or decrypted downloads from your computer.
What does a successful result mean?
Content and layout verified means the encrypted content and its structure passed the checks using the matching exported key. It does not prove who authored the file, when it existed, or that it is the latest revision.
Protected metadata, original key wrapping, and external freshness remain unverified by the public content-key reader. For example, the result does not independently authenticate the file's protected metadata or prove that the server still grants access. It is not the author's digital signature.
These are PhotonFile-published tools, not an unaffiliated audit. Read about the trust model and release evidence.
If something does not work
- The application is unavailable
- Try again shortly. If it persists, contact the site operator or use the Linux guide if downloads are available. This is a tool-availability issue, not a result about your file.
- Readiness fails or buttons stay disabled
- Do not select sensitive files until readiness succeeds. Reload the application and check whether your browser blocked required application assets. If it still fails, report the displayed error. Do not disable security checks to continue.
- The package or key is rejected
- Use the exact pair from a completed export. The package limit is 256 MiB and the key-file limit is 64 KiB. If a fresh matching export still fails, preserve the error for troubleshooting without sharing your key.
- Decrypt is disabled
- Verify successfully first. Reset, changing either input, or another operation invalidates the earlier verification.