A failed Rewind can mean that there is no snapshot, the saved copy is incomplete, or the archive service isn’t responding. It helps to identify which one you’re seeing.
Check the original page
Open the article itself, rather than the publisher’s homepage, a search result, or a social-network redirect. Start WebRewind from that page. An archive lookup depends on the page address.
Check extension access
If WebRewind doesn’t appear or cannot start, review the extension in your browser’s settings. On Safari, enable WebRewind and check website access. On Chrome, make sure the extension is enabled. Follow the setup steps.
Wait for a busy archive
Archive services sometimes load slowly or show a CAPTCHA. Keep the tab open, respond to any challenge, and try again if the service reports a temporary problem. Repeated clicks won’t make a missing capture appear.
Try another archive site
Choose another archive site in WebRewind’s settings. A different host can help with connectivity, but the five supported hosts can share captures. Treat this as a troubleshooting step, not a guarantee.
If the snapshot contains a paywall
The archive may have saved the same subscription prompt you see. A snapshot can also lack text, images, or newer corrections. WebRewind cannot recover content absent from the saved copy.
Try a publisher gift link, a library, institutional access, or a direct subscription for the current article. Learn how snapshots differ from live pages.
Get help with WebRewind
If the extension itself is failing, email hello@webrewindapp.com with your device, browser, app version, and the steps you took. Remove private details from screenshots. For billing or restore questions, visit support.
Journalism comes at a cost. For publications you value, consider supporting them directly with a subscription.