Diagnose
Classify the PST structure and determine whether a supported recovery path is credible.
Outlook data file recovery
Repair damaged Outlook PST files.
Diagnose the damage first. Preserve recoverable mailbox data. Pay for repair only when the evidence supports a trustworthy result.
Internal preview — upload validation only; analysis is not attached
Start with the file you have
Is your PST a fit for the private beta?
Preview uploads go directly from this browser to private Cloudflare storage. This test stops before analysis.
- Outlook .pst files
- Damaged indexes or structural metadata
- Mailbox content that may still be intact
Select an Outlook PST
Select a synthetic PST to test private resumable upload.
Complete the private upload verification before starting a new upload.
Preview upload
Private multipart transfer
Preparing upload…
PST parts go directly to private R2 storage. The API receives control metadata only. Analysis compute is not attached.
0%
Private beta
Your PST may fit the initial recovery scope.
Production diagnosis is not live yet. Contact us to discuss a private test. Do not attach or send your PST by email.
The intended recovery path
Evidence first, artifact last.
A calm, bounded process for a file that may contain years of important email.
Recover
Preserve validated mailbox blocks and rebuild only the damaged structural metadata.
Verify
Check structural invariants independently before a candidate can be selected.
Download
When production launches, verified results will be delivered through an authorized private download.
Recovery philosophy
Your mailbox is not a place to improvise.
CorrectPST’s initial repair strategy is intentionally narrow: retain validated content, reconstruct damaged indexes, and decline cases that require inventing data or resolving unsafe ambiguity.
That means some files will be classified as unsupported or unrecoverable. A clear decline is better than a plausible-looking PST that cannot be trusted.
Privacy by construction
Email contents stay out of analytics.
The internal preview sends PST parts directly to private Cloudflare storage; filenames, paths, exact sizes, capabilities, signed URLs, and PST-derived data stay out of analytics.
Future production storage, encryption, access, and deletion behavior will be documented before uploads are enabled.
Read the current privacy detailsQuestions before recovery
What to expect from CorrectPST
What PST problems is CorrectPST intended to handle?
The first repair path focuses on Unicode Outlook PST files whose mailbox content remains substantially intact but whose structural indexes or related metadata are damaged. Broader corruption and OST conversion are not currently supported.
Will I know whether recovery is possible before paying?
That is the intended product flow: diagnose first, explain the recoverable scope, and only offer a paid repair when the evidence supports a trustworthy result. Pricing and production diagnosis are not live yet.
Will a repaired PST work in Outlook?
Candidate files must pass structural verification before they can be offered. Outlook compatibility is a required release gate, but no repair tool can honestly guarantee recovery for every damaged PST.
What happens if the file cannot be safely recovered?
CorrectPST is designed to decline ambiguous or unsafe repairs rather than invent mailbox data or silently choose between conflicting revisions.
Does this page upload my selected PST?
This internal preview can upload a selected synthetic PST directly from your browser to private Cloudflare storage. The control-plane Worker never receives the PST body, and analysis is not attached.
Does CorrectPST support OST files?
Not in the initial scope. The private beta is focused on Unicode PST repair, not OST-to-PST conversion.
Have a damaged PST?
Validate a private resumable upload.
This internal preview accepts synthetic PST files and stops at ready for compute.