Please note that the December 29, 2025 date referenced in the article refers to 12:00 a.m. Pacific Time (PT).
All other dates and times are in Singapore Time (SGT). The backup window is also shown in the corresponding U.S. Eastern and Central European time zones.
Important: This article is for users affected by the Manus service change who use WebDev or operate a Manus-hosted website. First, check the notice in your Manus account and review What’s Happening and Am I Affected? to confirm whether your personal or team account is affected.
Whether a WebDev project or deployed website is in scope depends on the notice for the personal or team account that owns it. For affected Type A/B accounts, a website is in scope if its WebDev task was created or updated on or after December 29, 2025 at 12:00 a.m. Pacific Time (PT). A website completed before that cutoff and never updated afterward remains outside the task-deletion scope. For affected Type C accounts, the account and all associated WebDev data are in scope. Your email and in-app notice are the source of truth for the exact deletion scope.
Complete the official Task Data Backup before 7:59 a.m. Singapore Time (SGT) on August 23, 2026.
Affected deployed websites and services that depend on Manus will be unavailable from 8:00 a.m. SGT on August 23 until you actively complete Task Data restoration. Starting at 8:00 a.m. SGT on August 25, 2026, you can restore your data.
After you restore your Task Data Backup, a website that was deployed when the backup was created is automatically redeployed to the version captured by that backup. A project that was not deployed when the backup was created remains undeployed. You can review the deployment status and any deployment error in the related WebDev task.
Before reopening the website to users, verify the project data, deployment, domain, TLS certificate, configuration, integrations, and critical website functions.
Key timeline for WebDev users
Stage | What happens to WebDev | What you can do |
Before 7:59 a.m. SGT on August 23 | Your project and deployed website remain available. A backup captures your data at the time it is created and does not automatically include later changes. | Create the official Task Data Backup. Create another backup after important changes and confirm that every backup package is present. |
8:00 a.m. SGT on August 23 to 7:59 a.m. SGT on August 25 | Affected users cannot access Manus. Affected Manus-hosted websites and Manus-dependent services are unavailable during this period. | Do not expect the backup itself to keep the website online. Independently hosted services may remain available, but functions that depend on Manus will not operate. |
Starting at 8:00 a.m. SGT on August 25 | The restoration portal opens. The website does not return merely because the portal has opened. After you complete Task Data restoration, a website that was deployed when the backup was created is automatically redeployed to the backed-up version. A project that was not deployed at that time remains undeployed. | Restore the correct account or team first if required, restore your Task Data, and complete the post-restoration checks in this article. |
What is included in the WebDev Task Data Backup?
The official Task Data Backup is the restoration package for supported Manus-hosted WebDev project data. Export to GitHub to provide additional code redundancy, but it does not replace the official Task Data Backup.
Third-party connector configurations are restored with Task Data restoration, but the connectors must be manually re-enabled afterward. Some services may also require reauthorization. Do not rely on a restored integration until the connector has been re-enabled and its related workflow has been tested.
WebDev item | Backup and restoration guidance |
Project records and checkpoints | Supported project records and checkpoints are included. |
Code and Git data | Supported code and Git data are included. |
Manus-hosted project database | The project database is included. |
Form submissions, orders, and historical records | Records stored in the Manus-hosted project database are included. After restoration, check recent and business-critical records. |
Project storage and S3 files | Supported project storage and S3 files are included. Verify important uploads, images, and other media after restoration. |
Website SEO configuration | Supported SEO configuration is included. Verify important metadata, canonical URLs, redirects, robots directives, and sitemap behavior after restoration. |
Scheduled-task configuration | Scheduled-task configuration is included. Before relying on a scheduled task, verify its enabled status, time zone, next scheduled run, and connector or authorization dependencies. |
Project-level application keys and environment variables | Supported project-level values are included. This does not guarantee that every third-party API key, OAuth token, or runtime-generated value will return in its previous form. Verify all required values after restoration. |
Integrations (Shopify and Stripe) | Shopify and Stripe integrations are restored, but may require reauthorization. |
Independently managed third-party databases or services | These are not deleted or restored by Manus. They remain with the third-party provider, but you should verify the connection after restoring the WebDev project. |
What should I do before the deletion period?
First, open Backup & Restoration and follow How to Back Up Your Data to create the official Task Data Backup. If the relevant personal account is Type C, complete the account-backup step shown in Backup & Restoration first, and then create the Task Data Backup. For a team project, only the team owner can complete the required team backup. Personal and team workspaces must be backed up separately.
If you currently sign in only with Facebook, add an alternative login method or email address before starting the backup. Facebook login will not be available after the service change.
Confirm that you are backing up the personal or team account that contains the WebDev project.
Include the relevant WebDev tasks and projects in the Task Data Backup.
Confirm that every backup package is present in the selected cloud drive or local destination. Large backups may be divided into multiple packages. Do not modify, rename, or move the backup packages.
Create another backup after important changes to the project, database, files, or configuration. An earlier backup does not automatically update itself.
If you separately use a Cloud Computer and need files stored in its file system, compress and download those files before the deletion period. Cloud Computer file-system files are not included in the Task Data Backup.
If you also keep the code in GitHub, treat it as an additional code copy—not as a replacement for the official Task Data Backup.
A Cloud Computer instance does not run during the deletion period. Its public address, processes, web services, certificates, firewall rules, Forge Maps, and dependent calls are unavailable while the instance is stopped. The instance becomes available again after the related Task Data is restored. Before resuming production use, verify its files, configuration values, credentials, public address, processes, certificates, and firewall rules.
Important: The backup preserves supported data for later restoration. It does not prevent the affected website from becoming unavailable during the deletion period and until you actively complete Task Data restoration.
What happens during the deletion period?
From 8:00 a.m. SGT on August 23 through 7:59 a.m. SGT on August 25, affected users cannot access Manus. Affected deployed websites and Manus-hosted project services are also unavailable during this period. After the restoration portal opens, the website remains unavailable until you actively complete Task Data restoration.
Visitors to an affected Manus-hosted website see a neutral, unbranded maintenance page with the following message: “This site is under maintenance. We apologize for the inconvenience and appreciate your patience. Please check back later.”
Website paths return HTTP 503 Service Unavailable with a system-managed Retry-After header. Users cannot set the Retry-After value or date. The exception is /robots.txt, which remains available with HTTP 200 and continues to allow crawling. The same behavior applies to custom domains and manus.space addresses.
This treatment is intended to signal that the outage is temporary and reduce risk to already indexed pages. It does not guarantee that rankings, indexing, search-result freshness, or crawl timing will be completely unaffected.
A website that is not hosted in Manus generally remains with its own provider.
However, any function that depends on a Manus-hosted backend, authentication service, API, synchronization process, or webhook will not operate while that Manus dependency is unavailable. Forge API access for affected users and webhooks sent to an unavailable Manus-hosted site will also be unavailable during this period.
During this period, WebDev Schedules fail because the WebDev scheduler service is unavailable. Missed WebDev Schedule runs are not replayed after restoration. This statement refers to WebDev Schedules, not Manus Scheduled Tasks.
Website visitor login, built-in AI/LLM features, file uploads, maps, and other affected Manus-hosted capabilities are unavailable while the related service is stopped.
For affected Type A, Type B, and Type C users, Forge API access is unavailable during this period. Webhooks sent to an unavailable Manus-hosted website return a 5xx response and are not queued or replayed by Manus. An external webhook sender may still retry according to that sender’s own policy. External database connections to the unavailable website service also fail during this period.
What happens to custom domains, DNS, and HTTPS?
DNS records managed through an external DNS provider remain under that provider’s control and are not deleted by Manus. During the deletion period, however, the affected Manus-hosted website is unavailable even if the external DNS record still exists.
Domain restoration behavior depends on the domain type:
Domain type | What happens and what to check |
Default manus.space address | The original address is restored with the related Task Data. |
Custom manus.space subdomain | The same subdomain is restored if it is still available. Restore promptly: Manus cannot guarantee that a custom manus.space subdomain will remain unclaimed before you import the backup. |
Custom domain hosted outside Manus | External DNS records remain with the existing provider and are not deleted by Manus, including configurations that use external nameservers. The previous project-domain binding is preserved and reconnects automatically after Task Data restoration, but you must verify it manually. |
Domain purchased through Manus | The domain remains registered and is temporarily managed by Manus during an affected Type C account deletion. If a project-domain relationship existed before backup, the domain is automatically associated again after account restoration. Deletion does not remove its DNS records. Refer to the official refund-policy article for the applicable purchase-fee policy. |
After Task Data restoration, verify each of the following before treating the custom domain as fully restored:
Check | What to verify |
Domain binding | Confirm that the custom domain is connected to the restored deployment. |
DNS resolution | Confirm that the domain’s A, CNAME, or Nameserver configuration resolves to the intended restored target. |
HTTPS/TLS | Open the website over HTTPS and confirm that the certificate is valid and no browser warning appears. |
Canonical URL and redirects | Confirm that the preferred domain, www or non-www behavior, and important redirects work as expected. |
After restoration, open the related WebDev project, use the right-side panel to go to Settings → Domains, and confirm that every required domain binding is still present. Open each domain and verify that the website is reachable. If a domain does not work, disconnect it and reconnect the same domain.
Domains purchased through Manus normally do not require the user to edit CAA, DNSSEC, root-domain, or www records when binding the domain to a project. A domain hosted by another provider may require the user to update records at that provider.
If reconnecting a domain triggers TLS certificate reissuance, certificate availability may take several hours. Do not treat the domain as fully restored until HTTPS works without a browser warning.
If your domain was purchased through Manus and your Type C account is affected, see Refunds’ Timeline, Calculation, and Special Cases for the applicable domain policy.
Should I migrate the website or temporarily change DNS?
Manus does not provide an official method to migrate the complete Manus-hosted WebDev service elsewhere for the approximately two-day deletion period. A source-code or GitHub export alone does not include the complete database, uploaded files, configuration, and Manus-hosted capabilities. We strongly advise against attempting a full temporary migration solely for this event because it is difficult to reproduce the complete service and a seamless return cannot be guaranteed.
Do not change DNS solely for SEO reasons. If you have a specific business-continuity need and use a custom domain, you may temporarily point that domain to a simple externally hosted maintenance or status page before the deletion period.
For a domain whose DNS is managed through Manus, use Settings → Deployments → Domains. For a domain hosted elsewhere, make the change through the existing DNS provider.
A temporary DNS change may affect automatic reconnection after restoration. After restoring the Task Data, verify the project-domain binding in the WebDev project under Settings → Domains. If the domain does not work, reconnect it and restore the intended DNS configuration.
How do I restore and verify my WebDev website?
Follow How to Restore Your Data for the restoration-tool steps. Type C users must restore their account before restoring Task Data. For a team project, the team owner must complete the required account, team, and Task Data restoration steps.
There is currently no deadline to complete restoration after the portal opens. However, the affected website remains unavailable until the relevant Task Data Backup is actively restored, so restoring promptly shortens the downtime.
Restoration returns the project to the state captured by the selected backup packages. If the website was deployed when the backup was created, it is automatically redeployed to that backed-up version. If it was not deployed at that time, it remains undeployed.
Restoration can be completed only once. If your backup was divided into multiple packages, confirm that you have selected all required packages and that they contain the latest data before completing restoration.
Restoring Task Data is only the first step. Do not consider a production website fully restored until the checks below pass.
Area | What to check after restoration |
Deployment | Confirm that the expected version is deployed and the intended URL loads. |
Database | Check the database structure, record counts, recent records, form submissions, orders, and other critical business data. |
Files and media | Open representative images, uploads, documents, and generated files. |
Application configuration | Verify required environment variables and application keys without exposing secret values. |
Domain and HTTPS | Confirm domain binding, DNS resolution, HTTPS, and certificate health. If a domain does not work, reconnect it under Settings → Domains. If reconnection triggers certificate reissuance, allow for a delay of several hours. |
Scheduled tasks | Confirm enabled status, time zone, next run, and connector or authorization dependencies. Runs missed during the deletion period are not replayed. |
Authentication and permissions | Test sign-up, sign-in, account permissions, and OAuth flows used by the website. |
External APIs and services | Test critical email, payment, communication, database, and other third-party integrations. |
Forge API and webhooks | Confirm that Forge API requests are accepted and that webhooks are received and processed after restoration. Requests that failed during the deletion period are not replayed by Manus. |
SEO | Verify page metadata, canonical URLs, robots directives, sitemap behavior, and important redirects. |
Critical user journeys | Test the workflows your users rely on, such as registration, submitting a form, placing an order, receiving an email, or completing a payment. |
Connectors | Manually re-enable each restored third-party connector, complete reauthorization if prompted, and test the related workflow. |
Cloud Computer, if used | Confirm that the instance, required files, public address, processes, web services, certificates, firewall rules, Forge Maps, configuration values, and credentials are available and correct before resuming production use. |
Do not reopen a production website to users until the expected deployment, database records, files, domain, HTTPS certificate, WebDev Schedules, authentication, connectors, external integrations, Forge API, webhooks, SEO behavior, and critical user journeys have been verified. If a business-critical check fails, keep the website in a controlled maintenance state and contact Manus Support before resuming normal traffic.
If you have any questions, you can contact our customer service team at support@manus.im or use the support tool at the bottom right corner of this page. We’re here to support you through every step of the process.