Petit Planet Final Beta

The Petit Planet Final Beta has ended. It began on September 20, 2026, and the official news list records its conclusion on October 19, 2026. Old sign-up instructions and invitation videos are historical; they do not provide an active route into the game today.

The test was limited access, data wipe, and without in-game purchases. The next announced public release is December 4, 2026 for PC, iOS, and Android. Keep the historical rules below separate from the public release's requirements and account policies.

Final Beta timeline

The original sign-up FAQ said the end date would be announced later. That was accurate when it was written, but the later end notice resolves the question. Do not repeat “end date not announced” after the official news list has supplied the conclusion.

An old page title saying sign-ups are open can also outlive the application period. The dated timeline is more useful than the wording left in a search result or video title.

What limited access meant

The Final Beta selected a limited number of participants. Submitting a sign-up survey applied for access; it did not guarantee a place. Selected players were sent an invitation and download guide by email before testing began.

The official application route asked players to complete the survey on the Petit Planet website. Community events offered another chance to obtain test access. Those routes belonged to the test period, rather than a paid public preorder.

A valid email address mattered because the invitation and download instructions were sent there. Survey answers could not be edited after submission, so the application instructions emphasized checking email, account, and device information before sending the form.

Today, correcting an old survey or finding an old invitation does not reopen the ended test. If you missed the application period, follow the public release information rather than trying to complete a historical application.

Returning testers and the Luca Arbor condition

Players from the Coziness Test or Stardrift Test could also be considered for Final Beta access. The announced conditions included reaching Luca Arbor Lv. 3 in one of those earlier tests and still completing the Final Beta sign-up survey with accurate information.

That history matters when interpreting a post saying previous testers could return. It did not mean every old account automatically had unrestricted access, nor that reaching the level after a closed test could create a new invitation.

The level condition was an access rule for returning testers. It was not a public-launch starting level, a pre-registration reward requirement, or a promise that old progression would be retained.

Supported platforms in the test

The Final Beta supported Windows PC, iOS, and Android. Emulators were not supported in that test. All selected participants received PC access; mobile access was assigned as either iOS or Android based on the device information in the application.

If a participant did not report a compatible mobile device, that participant did not receive mobile access. An invitation therefore did not necessarily mean every supported platform was enabled for that account.

The Windows wording is specific. It does not establish a native Mac edition. Similarly, iOS support did not imply that a player could freely alternate between every Apple device. The binding rules below restricted the hardware used for that account.

The official test recommendations

These specifications describe the Final Beta recommendations, not final public-launch minimum requirements.

These are complete recommendation groups. Taking only the operating-system row does not establish that every device on that OS met the test's hardware recommendation. Likewise, a later phone name alone does not prove a particular performance result.

The current App Store listing says iOS or iPadOS 15.0 or later. Do not replace that release-facing listing with the older test's iOS 14.0 figure when deciding whether to use an iPhone at public release.

Historical Final Beta recommendations, not final public-launch minimum requirements.

One bound PC and one bound mobile device

During the Final Beta, each account could use up to one PC and one mobile device, with mobile being the assigned iOS or Android platform. The first devices used to log in became bound to the account.

Switching to another device on the same platform could result in account suspension and loss of test participation. The instructions explicitly counted moving from an iPhone to an iPad as changing an iOS device. Sharing an Apple ecosystem did not make them the same bound device.

The test instructions also told players to avoid hardware replacement, operating-system reinstallation, mobile OS upgrades, and factory resets after installing the client. Such changes could be recognized as changing devices under that test's rules.

These restrictions explain why historical advice emphasized choosing the first login device carefully. They are not a verified claim that the same restrictions will apply to all public players after release.

Cross-platform data during the test

The Final Beta allowed game data to carry between the bound PC and mobile device when both used the same HoYoverse Account. That was a specific test arrangement for an account's permitted hardware.

It did not allow arbitrary additional phones or computers. A player needed both the assigned access and the correct account; the data-transfer statement did not cancel the device limit.

It also does not establish the final public release's cross-save rules, a future Switch 2 transfer process, or shared purchases between every platform. Those questions need release-specific information. Keep the historical fact useful by retaining the conditions that made it true.

Data wipe and the end of progression

The Final Beta was a data-wipe test. The official rule said that when testing ended, the servers would close and test account information and game data would be deleted unless otherwise authorized.

That means a beta inventory, home layout, relationship level, or collection should not be assumed to carry into public release. A recording or screenshot may preserve what a player made, but it is not an in-game transfer entitlement.

Pre-registration rewards are a separate launch campaign. Registering interest does not turn an old test save into public progression, and the data-wipe rule does not mean that the separate launch rewards disappear. Treat those two systems according to their own instructions.

Purchases and account use

There were no purchases available during the Final Beta, either in the client or through the official website. The test's free access did not establish that the released game would have no optional purchases; the current mobile stores disclose them.

Access was personal. Transfer, account sharing, lending, and selling access or the test client were prohibited. The official rules said access could be revoked for violations and that suspensions for the specified sharing or device-change issues were not appealable under the test policy.

These rules explain why buying a leftover invitation would not be a legitimate public-release route. Now that the test has ended, the practical route is the announced public launch rather than a transaction involving old test access.

Internet connection, languages, and sharing recordings

The test required an internet connection throughout play. It listed English, Japanese, French, Indonesian, Thai, Russian, German, Spanish, Italian, Korean, Portuguese, Turkish, Vietnamese, Simplified Chinese, and Traditional Chinese.

The language list describes supported test languages. It does not separately guarantee that every line had voice acting in every listed language.

The test permitted players to share gameplay through screenshots, recordings, and livestreams subject to its stated rules. That is why a public video can show detailed systems from a closed test. Publicly visible footage does not mean the server remains open or that the recorded feature is unchanged for release.

What to do after the test

Use the December 4 public-launch information to choose your platform and follow the official store or client route. Check current compatibility rather than copying the beta's recommended specifications into a release checklist.

If you are interpreting an old tutorial, first identify whether it belongs to Coziness, Stardrift, or Final Beta. Keep its account, device, language, and progression conditions attached to that build. The Final Beta is useful context for how the game developed; it is no longer an active sign-up opportunity.