# TikTok has retired HTML mini games — developers must rebuild them for its native runtime

TikTok stopped accepting HTML mini games on August 28 and retired existing online HTML games on September 9. Affected developers cannot simply repackage their web builds: TikTok requires a native-runtime rebuild, with legacy HTML platform data scheduled for deletion on September 30.

This is a platform migration with a real rewrite boundary. Existing HTML games need to be rebuilt through Unity, Cocos or Laya, then have login, ads, purchases and other TikTok capabilities reintegrated and retested before relaunch.

- Status: Active
- Published: 2026-09-11T06:34:14+12:00
- Updated: 2026-09-11T06:34:14+12:00
- Categories: Web Development, Marketing & Distribution, Developer Tools, Marketplaces & Platforms
- Tags: migration, mini games, TikTok, TikTok Minis
- Canonical HTML: https://beyondthe.news/dossiers/tiktok-mini-games-html-h5-native-runtime-migration-september-2026

## What changed

TikTok has sunset the HTML/H5 runtime for Mini Games. Its migration documentation says HTML games stopped being accepted or supported on August 28, 2026, existing online HTML mini games were retired on September 9, and legacy HTML data on the TikTok Minis platform is scheduled to be cleared and deleted on September 30. TikTok does not provide automatic conversion. Developers who want to keep an affected game running must back up the old project and relevant user/business data, rebuild for TikTok's native mini-game runtime using a supported engine workflow, reintegrate platform capabilities, test on real devices, pass review and launch the replacement.

## Why it matters

A runtime retirement is much more disruptive than a normal SDK deprecation. HTML/CSS/JavaScript games that previously ran in a WebView cannot be kept alive by renaming files or uploading the old web bundle. TikTok's native mini-game path changes the packaging, runtime and testing model and can require rebuilding platform integrations around login, authorization, advertising, purchases, sharing and user state. The September 30 data-clearing date also makes backup work time-sensitive even for developers who do not plan to complete the migration immediately.

## The old runtime is already past its operating deadline

TikTok's timeline is not merely a future warning. New HTML mini games stopped being supported on August 28, and online HTML games were retired on September 9. Continuing operation now requires a native version rather than leaving the existing H5 build in place.

## There is no automatic HTML-to-native conversion

TikTok explicitly says a standard website, game URL, web build directory or HTML ZIP cannot be converted directly into a native mini-game package. Developers need a source project built through supported native-runtime tooling such as Unity, Cocos or Laya and must export it in the package format TikTok expects.

## Platform capabilities have to be integrated again

The migration checklist includes revalidating login and authorization, in-app ads, in-app purchases, sharing and revisit capabilities. That means teams should treat the work as an application migration with regression testing rather than a build-system switch.

## September 30 is a data-retention boundary

TikTok says it will clear and delete legacy HTML platform data on September 30. Developers are told to back up code, assets, configuration, server API details and any business or user data they need to retain before that date.

## The native runtime changes the execution model

TikTok's current technical documentation describes native mini games as code packages executed by TikTok's mini-game runtime, with the client responsible for rendering, input, audio, file and network operations. JavaScript or WebAssembly can still be part of the game, but the deliverable is no longer an ordinary web application running in a WebView.

## Key details

- HTML/H5 mini games stopped being accepted or supported on TikTok Minis on August 28, 2026.
- Existing online HTML mini games were retired on September 9, 2026.
- TikTok says legacy HTML platform data will be cleared and deleted on September 30, 2026.
- There is no automatic converter from an HTML/WebView game to the native runtime.
- A regular website, HTML ZIP or unadapted web build cannot be uploaded directly as a native mini game.
- TikTok's supported native workflows include engines such as Unity, Cocos and Laya.
- Affected games need platform capabilities such as authentication, ads and purchases revalidated after migration.

## Builder takeaways

- Back up every affected HTML project and its configuration/business data before September 30 even if the native rebuild will happen later.
- Do not scope this as a packaging-only job; inventory login, authorization, ads, purchases, sharing, revisit flows and server-side state as separate migration work.
- Plan for real-device testing and TikTok review time because the old HTML version can no longer serve as the production fallback.
- If a game started as a portable web build, estimate the cost of maintaining a TikTok-specific native-runtime target before deciding whether continued distribution on the platform is worth it.
- Keep user entitlement and purchase-state migration explicit so a runtime rewrite does not strand paid or returning users.

## What to watch

- Whether TikTok extends or changes the September 30 legacy-data deletion schedule.
- Additional migration tooling or compatibility layers for former HTML games.
- Changes to supported engines, package limits and native-runtime APIs as the platform standardizes around the new path.
- How TikTok handles existing purchases, entitlements and user-state edge cases during late migrations.
- Whether the HTML retirement changes developer adoption or the mix of games distributed through TikTok Minis.

## Uncertainties

- TikTok's public documentation does not establish how many active HTML mini games are affected.
- Migration effort will vary substantially by engine, game architecture and use of TikTok-specific capabilities.
- The exact handling of every legacy data type should be confirmed by affected developers against their project and platform account before deletion.

## Sources

- [Migrate from HTML to Native Runtime](https://developers.tiktok.com/docs/en/migrate-from-html-to-native-runtime) — TikTok for Developers · primary migration documentation · 2026-09-04T00:00:00+12:00. Primary sunset timeline, backup/deletion warning, no-automatic-conversion boundary and migration checklist.
- [Mini Games Technical Overview](https://developers.tiktok.com/docs/en/mini-games-technical-overview) — TikTok for Developers · primary technical documentation · 2026-09-01T00:00:00+12:00. Current native-runtime execution model, supported engine workflows and warning that ordinary HTML/web builds cannot be delivered directly.
- [Develop Your Mini Game](https://developers.tiktok.com/docs/en/develop-your-mini-game) — TikTok for Developers · primary developer documentation · 2026-08-28T00:00:00+12:00. Current integration workflow for native-runtime mini games and platform capabilities.