Source-referenced editorial guide. No hands-on Hostinger product test, price, discount, ranking or measured outcome claimed.
A full restore can replace files and database; a narrower restore may preserve more recent work. Hostinger notes that restoring returns the site to its earlier state.
Define what you need to recover
A full restore can replace files and database; a narrower restore may preserve more recent work. Identify whether the failure is missing files, corrupted data, an unwanted content edit or a configuration change before choosing the restore type.
Protect changes made after the backup
Hostinger notes that restoring returns the site to its earlier state. Export recent orders, submissions or new articles if the site still allows it. Download the current state before proceeding so you can retrieve something that was created after the chosen backup.
Choose the correct backup date
Use the last known good point, not simply the newest backup. If malware or corruption existed before the latest backup, restoring it will not resolve the underlying problem. Compare timestamps with logs and reports of when the problem first appeared.
Verify after restoration
Check representative URLs, login, images, forms and any payment or enquiry flow. Clear caches only after confirming the server has the right content. Then investigate the original cause so the same issue does not recur.
Plan the communication
Tell editors when to stop making changes and when they can resume. For a store, account for orders placed during the recovery window. Document what was recovered and what, if anything, must be recreated.
Post-restore evidence
Save screenshots of the broken and recovered pages, plus the backup timestamp and restore history. Compare an anonymous browser session with the admin view. If a form or checkout now works, submit a real test and inspect the delivered message or test order rather than relying on visual appearance alone.
Source and editorial note
Primary source: www.hostinger.com
Prepared from official documentation and general implementation practice. This guide does not claim a hands-on test, a measured result, a live price or a guaranteed outcome. Check current plan and product details before changing a production site.
Put it into practice
Choose one step from this article, try it on a representative project, and record what you learn before changing the wider workflow.
This is general editorial guidance rather than a hands-on product test; verify platform-specific details in current primary documentation.
Take it with you
From the community
Join the conversation.