Starter
$29.99/ month
100 page credits each month
For a small archived website or one focused recovery.
- Effective rate
- $0.30 / page
- Saving
- Base rate
Monthly Website Recovery Plans and Page Credits
Plus
$59.99/ month
250 page credits each month
For broader company sites and established content libraries.
- Effective rate
- $0.24 / page
- Saving
- 20% / page
Pro
Recommended$149.99/ month
750 page credits each month
For deep archives with several page families and templates.
- Effective rate
- $0.20 / page
- Saving
- 33% / page
Scale
$299.99/ month
2,000 page credits each month
For substantial websites and high-volume recovery work.
- Effective rate
- $0.15 / page
- Saving
- 50% / page
Included in every monthly plan
The allowance changes by plan. The recovery workflow and supported output formats do not.
- Credits reset every month
- All supported output formats
- Required assets tracked separately
- Recovery manifest and limit report
The site inventory recommends the smallest plan that covers the estimated normalized page count before Stripe Checkout opens. Generated packages remain available for 90 days from creation.
How the volume discount works
The discount is measured against the Starter rate of about $0.30 per page. Credits cover normalized public pages across recovery jobs in the active monthly billing cycle. Required images, styles, scripts, fonts, and documents do not reduce the page balance.
| Plan | Monthly page credits | Monthly price | Effective price per page | Per-page saving |
|---|---|---|---|---|
| Starter | 100 | $29.99 | $0.30 | Base rate |
| Plus | 250 | $59.99 | $0.24 | 20% |
| Pro | 750 | $149.99 | $0.20 | 33% |
| Scale | 2,000 | $299.99 | $0.15 | 50% |
Unused page credits expire when the monthly billing cycle ends and do not roll over. The renewed allowance is available after Stripe confirms the next subscription period.
Compare the recovery outputs
Choose the format that supports the way your team will edit, host, and maintain the recovered site. The format choice does not add a surcharge.
| Output | Best for | What you receive | What still needs new work |
|---|---|---|---|
| HTML, CSS, and JavaScript | Brochure sites, portfolios, archives, and simple content | Portable pages, assets, manifest, and reports | Accounts, private data, server search, checkout, and form processing |
| WordPress | Teams that need to edit pages, posts, media, and menus | Structured content, theme templates, media mapping, and redirect plan | Custom application behavior and data that was never public |
| React, Next.js, Flask, Django, Vue, or Astro | Teams that maintain a framework project with reusable components | A project in the selected format, recovered content, assets, manifest, and setup instructions | Private features, integrations, and data outside the approved public recovery scope |
How scope is determined
We count distinct recoverable URLs after normalization, then review the number of templates, external asset hosts, missing dependencies, and required application features. A thousand duplicate tracking URLs do not become a thousand billable pages.
What is never promised
A public web archive cannot restore a private database, passwords, unpublished files, server configuration, or a working checkout system. We identify those gaps before work begins and quote new implementation separately.
Try the free front-page rebuild, then read the full restoration workflow.