Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The official migration notice now states that H5 is no longer accepted or supported from August 28, 2026, live H5 mini games retire on September 9, and old HTML data is cleaned up on September 30. This site’s previous September 4 statement has been corrected.
- The platform will not automatically convert a web build into a native package. Renaming files, changing a URL or recompressing them does not constitute migration.
- Migration requires more than rebuilding the client. Login, authorization, ads, payments, sharing, return-entry points and server-side entitlements all need to be revalidated.
- Local saved data will not automatically appear in the native runtime. A migration, restoration or reinitialization path must be designed.
- Passing preview is not production acceptance. Real devices, review packages, payment fulfillment and historical entitlements must be checked individually. General development and release guides still describe HTML formats, but that does not establish current H5 publishing eligibility. Project exceptions and actual export availability require separate verification.
Why preserve data first even if an old entry point still opens after September 9?
After September 9, a team may find an old H5 entry point occasionally accessible or still see its project in the Developer Portal, and mistake visibility for continued support. The official migration notice gives September 9 as the retirement date and schedules old HTML data cleanup for September 30. Entry-point status does not establish a project extension, and the notice alone does not prove that a particular project’s data has already been deleted.
First list affected projects and make verifiable backups. For code repositories, build assets, configuration, server APIs, account mappings, saved data, orders, balances and purchased entitlements, record locations, owners, export times and restoration tests separately. If the Portal no longer permits exports, retain the error and project ID and contact platform support. Do not overwrite originals or claim recovery is guaranteed.
Old and new rules: this is not an ordinary SDK upgrade
TikTok Minis’ general development overview still describes both HTML and Native runtimes, and the release guide still lists HTML5 package sizes. The dedicated migration notice, however, states that H5 is no longer accepted or supported from August 28, 2026, live H5 mini games retire on September 9, and old HTML data is cleaned up on September 30. Older format descriptions alone do not prove that H5 submissions are currently allowed. Plan migration using the dedicated notice, and confirm any written exception for an individual project with the platform.
Native mini games still run inside the TikTok App; teams are not being required to publish a separate standalone app. However, the build must be exported through an engine such as Unity, Cocos or Laya and its platform plugin. A standard website, web URL, web build directory or HTML ZIP cannot be uploaded directly as a native package, and no automatic conversion process exists.
Define project, data and user responsibilities before migration
This applies to development, publishing, payment and operations teams for existing HTML mini games on TikTok Minis. Businesses using only ordinary TikTok videos, TikTok Shop or H5 on independent websites should not apply this Minis runtime-retirement timeline to themselves. The migration notice lists no regional retirement exceptions. The release guide separately lists business verification, industry qualifications and native-publishing requirements for regions including the United States and Vietnam; those requirements do not prove an H5 extension. Verify project permissions and actual export availability through the Developer Portal and written platform responses.
Divide data into three groups: client assets that can be rebuilt from the code repository; progress and settings that depend on HTML local storage; and data stored in server-side account, order and entitlement systems. The second group will not automatically enter the native environment. The third must be read back and validated item by item using stable user mappings. If correct entitlement mapping cannot be demonstrated, stop the launch instead of clearing or overwriting old records.
Seven steps between retirement and September 30
First, freeze the H5 project version, make multiple backups and test sample restores. Second, before the September 30 cleanup, export any old data available through the platform and compare it with server-side saved data, orders and entitlement inventories; retain errors and contact support if export is unavailable. Third, choose a Unity, Cocos or Laya path supported by the official guide. Fourth, export a native build with the corresponding plugin. Fifth, reintegrate login, authorization, ads, in-app purchases, sharing and return-entry capabilities. Sixth, validate identity, saved data and payments in DevTool, on real devices and in the platform’s test environment. Seventh, allow time for review and necessary user notices, and switch to the native version only after actual production validation. The announced September 9 retirement date has passed, so the old H5 package cannot serve as a rollback plan.
Each step needs acceptance records: build version, Client Key, test account, device and TikTok client version, API results, and before/after values for orders and entitlements. Success in an emulator, local debug or preview does not establish that production payments and historical entitlements have been validated.
Failure, stop and rollback conditions
If the native package shows mismatched login identities, missing old saves, inconsistent balances or purchased entitlements, duplicate ad rewards or unfulfilled payment callbacks, immediately stop increasing traffic and retain read-only evidence from both H5 and native systems. Do not hide differences by deleting user records or issuing duplicate entitlements. Account, payment and game-data owners should reconcile them together.
Define rollback conditions before native launch. The announced September 9 retirement date has passed, so do not assume a return to H5 will allow continued operation. Rollback can cover a new native version, feature switches or traffic shares; backups of old HTML data must remain separately retained. Before September 30, revalidate that backups outside the platform can be restored. After the cleanup date, check the project’s actual status and subsequent official notices rather than assuming data was deleted solely because of the scheduled date.
Common mistakes and network boundaries
Common mistakes include treating sunset as a performance recommendation instead of a mandatory timeline; assuming the platform will automatically migrate IndexedDB or local files; checking only whether the first screen opens without testing payments, ads and historical entitlements; and blaming egress IP first when review fails. This change has no direct relationship to fixed egress, IP location or buying a proxy.
Only when logs explicitly show DNS, TLS, connection timeouts or upload-path errors should you use the proxy connection checklist to validate the transport layer separately. Package structure, engine adaptation, permissions, data migration and review outcomes will not be fixed automatically by changing IPs. Preserve error codes and build information first, then investigate using the official native-development guide.
Sources
Frequently Asked Questions
When does TikTok Minis stop supporting HTML/H5 games?
As of September 27, 2026, the official migration notice states that H5 is no longer accepted or supported from August 28, live H5 mini games retire on September 9, and old HTML data is cleaned up on September 30. Affected projects should back up data and test restoration before cleanup; verify each project’s actual status separately.
Can repackaging an H5 ZIP turn it into a native mini game?
No. The official explanation says a standard website, URL, web build directory or HTML ZIP cannot be converted directly. Rebuild and export a native package through a supported path such as Unity, Cocos or Laya.
Will users’ local saved data be retained automatically after migration?
No. The game must implement migration, restoration or reinitialization for progress, settings and files from the HTML environment, and reconcile them with server-side accounts and entitlements.
Is passing DevTool preview enough to launch?
No. Real-device tests, platform tests, review and production validation are also required, especially for login, ads, payments, historical entitlements, sharing and return-entry points.
Can we roll back to H5 after September 9?
Do not plan on that. The official notice lists September 9 as the retirement date for live H5 mini games. Design rollback for native versions and traffic switches rather than relying on continued operation of old H5 builds.
Will changing IPs help with migration or review failures?
It will not fix package-structure, runtime, permission, data or review problems. Investigate networking separately only when error evidence clearly points to DNS, TLS, timeouts or the upload path.