Manus’s data backup window for affected users closed at 7:59 p.m. EDT on August 22, 2026. The company says its restoration portal opened at 8:00 p.m. EDT on August 24, which is 8:00 a.m. SGT on August 25.
Direct answer
If you completed a backup, you can now use the Manus restoration flow. Type A and Type B users restore task data after login; Type C users must restore account data first, then task data. If you missed the deadline, Manus’s official pages do not promise a recovery path.
| Question | Current answer |
|---|---|
| Backup window | August 11 to 7:59 a.m. SGT on August 23, 2026 |
| US Eastern backup deadline | 7:59 p.m. EDT on August 22, 2026 |
| Deletion period | 8:00 a.m. SGT on August 23 to 7:59 a.m. SGT on August 25 |
| Restoration status | Open since 8:00 a.m. SGT on August 25 |
| US Eastern restoration start | 8:00 p.m. EDT on August 24 |
| Who should rely on this | Users who received a Manus email or in-app notice |
| Source of truth | Your Manus notice, plus the official Manus Help Center |
The next step depends on whether you have backup files. If you do, keep every package together and use the official restoration portal. If you do not, check your email and in-app notice, then contact Manus through its Help Center.
What is confirmed
Manus has confirmed these points in its blog and Help Center:
- Some users are affected by a service change tied to Manus returning to independent operations.
- The affected data scope depends on the account category shown in the user’s official notice.
- The backup window ended at 7:59 a.m. SGT on August 23, 2026.
- The deletion period runs from 8:00 a.m. SGT on August 23 to 7:59 a.m. SGT on August 25.
- The deletion period ended at 7:59 a.m. SGT on August 25.
- The restoration period started at 8:00 a.m. SGT on August 25.
- For Type A and Type B users, the Task Data Restoration Tool should appear after login.
- Type C users must restore account data first, then task data.
- Team owners, not ordinary team members, handle team restoration.
- Data restoration can only be completed once, so users should confirm all backup packages before submitting.
- Human and AI customer support were suspended during the maintenance window.
This is not a normal outage check. If Manus is unavailable and your notice says your account is affected, the official timeline is the first thing to check.
What is still unknown
Some details still depend on your account and backup files:
- Whether your account is Type A, Type B, Type C, or unaffected.
- Whether every task, generated artifact, connector, and WebDev project you care about was included in your latest backup.
- Whether a large backup was split into multiple packages.
- Whether team data was backed up by the correct owner.
- Whether a restored WebDev project will need domain, TLS, environment variable, database, or connector fixes.
- Whether a third-party integration needs separate reauthorization after Manus restores connector configuration.
Do not guess from social posts. Your email and in-app Manus notice decide the affected scope.
What to do if you already backed up
Use this checklist before submitting a restoration:
- Find the latest Task Data Backup package.
- If the backup was split into multiple files, keep all of them together.
- Do not rename, edit, unpack, or move packages unless Manus instructs you to.
- For Type C accounts, keep the Account Info Backup as well as the Task Data Backup.
- For team accounts, confirm whether the team owner has the team backup packages.
- Sign in through the official Manus site and open the restoration tool.
- Restore the correct account first if Manus requires account restoration.
- Upload or import all relevant backup packages before confirming the one-time restoration.
- After restoration, check tasks, files, connectors, and any generated websites before resuming normal work.
If your main concern is account safety, how to check if an app is safe has a general install and login checklist. For broader outage triage, see how to check if a website or app is down.
What to check for Manus WebDev projects
Manus gives WebDev projects their own restoration notes because a restored task is not the same as a verified production site.
| Area | What to verify after restoration |
|---|---|
| Deployment | The expected version is deployed and the URL loads |
| Domain | Custom domain binding still points to the right project |
| HTTPS | TLS certificates are active after restoration |
| Database | Important tables, records, forms, orders, or recent entries are present |
| Files and media | Representative uploads, images, and generated files open correctly |
| Configuration | Required environment variables and application settings are present |
| Connectors | Third-party connectors are re-enabled and tested |
| Scheduled work | Timers, automations, and connector-dependent jobs still run |
Manus said affected Manus-hosted websites could return HTTP 503 during the deletion period. The restoration portal opening does not automatically bring every site back; the owner still has to complete Task Data restoration.
If you missed the backup deadline
The official sources reviewed here do not promise a recovery path for users who missed the backup window. The safest next steps are:
- Confirm whether your account was actually affected.
- Search email for the Manus notice and any backup or refund messages.
- Do not share backup packages, refund receipts, or account files with unofficial helpers.
- Contact support through the official Help Center or support@manus.im.
Avoid “restore Manus data” ads, unofficial scripts, and anyone asking you to upload account backup files outside the Manus restoration flow.
Official sources
Manus Help Center’s what is happening and am I affected page explains the A/B/C account categories, the August 23-25 SGT timeline, affected data types, backup period, deletion period, restoration period, and account/team distinctions.
Manus Help Center’s how to restore your data page explains personal restoration, Type C account-first restoration, team-owner restoration, one-time restoration, multiple backup packages, and connector re-enabling.
Manus Help Center’s WebDev projects and websites page explains WebDev backup scope, affected website downtime, HTTP 503 behavior, restoration timing, and post-restoration checks.
Manus Help Center’s support availability page confirms customer support suspension during the August 23-25 maintenance window.
FAQ
When was the Manus backup deadline?
The backup deadline was 7:59 a.m. SGT on August 23, 2026. Manus also lists that as 7:59 p.m. EDT on August 22 and 1:59 a.m. CEST on August 23.
When does Manus restoration open?
Manus says restoration opens at 8:00 a.m. SGT on August 25, 2026. That is 8:00 p.m. EDT on August 24.
Is every Manus user affected?
No. Manus says unaffected users can continue normally. Affected users should rely on their email or in-app notice to confirm account category and data scope.
What if I have a Type C Manus account?
Manus says Type C users must restore the account first with the Account Info Backup, then restore task data with the Task Data Backup.
Will Manus-hosted websites stay online during deletion?
Manus says affected Manus-hosted websites and Manus-dependent services can be unavailable during the deletion period and remain unavailable until the relevant Task Data restoration is completed.
Can Manus data restoration be repeated?
Manus says restoration can only be completed once. Check that the selected backup packages are correct and complete before confirming restoration.