Where Did Seedance2.ai Go? Tracking Down the AI Video Tool’s New Home

The AI video generation service that operated at Seedance2.ai has not been discontinued. It changed its name and moved to a different domain, and is now available at seevio.ai.

Accounts, credit balances, active subscriptions, and previously generated videos were carried across to the new address. For most users the transition requires no action beyond signing in at the current domain and updating a saved bookmark. Integrations that call the service through its API require an endpoint change, described below.

Summary of the change

	Status
Service availability	Continuous; no interruption to generation
Accounts	Carried over; no re-registration required
Credit balances	Carried over unchanged
Subscriptions	Continue on existing cycle and pricing
Generated video library	Retained and downloadable
Model lineup	Unchanged
Domain and service name	Changed
API base URL	Changed
Card statement descriptor	Reflects the new name

About the service

The product is a browser-based AI video generation tool. Users supply either a text prompt or a still image, set parameters including resolution, duration, and aspect ratio, and receive a generated video clip. Generation runs as an asynchronous task: requests are queued, processed, and returned on completion rather than synchronously.

Usage is metered on a credit system rather than per-seat licensing. Credit consumption scales with the demands of the requested output, with longer durations and higher resolutions drawing down more than short, lower-resolution clips. Credits are available through subscription plans and one-off purchases.

The service provides access to multiple video generation models through a single account, with model selection made within the product at generation time. None of this changed with the move to the current domain.

Account access

The user database was not reset during the move. Accounts registered on the previous domain remain valid and sign in at the new one using the original email address or the original third-party sign-in method. There is no account migration step and no re-registration.

Two conditions account for most reported sign-in difficulties:

Credentials saved against the previous domain. Password managers that scope entries by hostname will not offer a stored password at a different address. The saved entry needs its URL updated, or the credential entered manually.

Sign-in method mismatch. Accounts created through a third-party provider have no password associated with them. Email-and-password sign-in will not succeed on such an account regardless of the credentials supplied; the original method must be used.

Users unable to sign in after addressing both should contact support with the original registration email address.

Credits and billing

Credit balances transferred at face value. No conversion, expiry, or re-denomination was applied as part of the move, and balances on accounts that have been dormant since before the change remain intact.

Recurring subscriptions continue uninterrupted on their existing billing cycle at their existing price, processed through the same payment provider as before. The merchant descriptor appearing on card statements now reflects the new service name. Users who do not recognise the descriptor should verify against their subscription status in the account dashboard before disputing a charge.

Subscriptions that were active before the move remain active. A user who stopped visiting the site during the transition and assumed billing had ceased should confirm the current subscription state in the dashboard, and cancel there if the plan is no longer required.

Invoices and payment records remain available through the account. Businesses requiring documentation issued under the current service name can regenerate invoices from the billing section.

Generated work

Videos produced before the change remain in the account library and can be downloaded as before. Retention terms are unchanged.

Direct video URLs issued under the previous domain are subject to the same redirect arrangement as the rest of the site. Where such URLs have been embedded in published content, stored in a database, or shared externally, they should be updated to the current domain rather than left dependent on forwarding.

API and integrations

The API base URL changed with the domain. Integrations still addressing the previous host will fail, in some cases silently, depending on client error handling.

Authentication credentials were not rotated. Existing API keys remain valid; only the host to which requests are sent requires updating.

Three items should be reviewed together:

• Base URL. Update the endpoint in all environments, including staging and any scheduled jobs that may not be exercised daily.
• Callback destinations. Integrations receiving asynchronous task-completion notifications should confirm callback configuration resolves to the current host.
• Stored URLs. Applications that persist generated video URLs will hold records referencing the previous domain. These should be rewritten rather than left to rely on redirects.

Deprecation schedules for legacy API hosts are generally shorter than for user-facing redirects. Teams running production workloads should confirm the retirement timeline for the previous endpoint directly with the operator rather than inferring it from redirect behaviour.

Old links and search results

Redirects from the previous domain to the current one are in place. These are a transitional measure and should not be treated as permanent. Documentation, internal references, published links, and browser bookmarks are better updated directly.

Browser behaviour accounts for a share of reported access problems during any domain change. Cached redirects, autocompleted address bar entries, and saved bookmarks can all route a returning user to a stale destination. Clearing the cached entry for the previous domain, or navigating to the current address directly rather than through autocomplete, resolves these cases.

Search engine results reflect domain changes with a delay. For a period following any move, results for the previous name may continue to surface the old address while the current one accumulates visibility. This does not indicate anything about the operational status of the service.

DNS propagation is also uneven. Users on different networks or resolvers may reach the new address at different times during the immediate transition window. A domain that fails to resolve on one connection but loads on another is exhibiting normal propagation behaviour rather than an outage.

Third-party listings — tool directories, review sites, and aggregators — update on their own schedules. Entries referencing the previous domain may persist for some time after the change and should not be read as current information about where the service operates.

Why the name changed

The service provides access to several video generation models rather than one, and the operator has said a name of its own reflects that more accurately. It also distinguishes the service from the model providers whose models it makes available. The model lineup itself was not affected.

Further information

The operator has published a migration notice covering sign-in behaviour, credit and subscription continuity, and the status of the previous domain in more detail. Users with questions not addressed there should contact support through the current site.