On July 1st, the PlayCanvas Editor will drop support for Engine V1.
Engine V2 has been the default Editor runtime for some time, and the Engine V1 Editor path has remained available as a deprecated fallback while teams completed their migration. From July 1st, the Editor will no longer support Engine V1 as an Editor option.
This change applies to the PlayCanvas Editor. Existing published builds are not modified by this announcement, but any project you continue to edit, launch, publish, or download through the Editor should be validated on Engine V2.
Before July 1st
Open each active project in the latest Editor and verify that it behaves correctly.
Switch projects to Engine V2 where possible.
Review visual differences, especially rendering, texture color space, post effects, and older script patterns.
Use the migration docs to address Engine V1 to Engine V2 differences.
On and after July 1st
The Editor will no longer support Engine V1.
Engine V1 Editor fallback options will no longer be available.
Projects should be edited and validated using Engine V2.
Existing published builds will not be changed by this update.
Engine V1 will remain in LTS and receive critical bug fixes only.
If you find a project that cannot be moved to Engine V2 before July 1st, please raise it on the forum, GitHub Issues, or Discord with a minimal repro and screenshots where possible.
@KPal what will happen to abandoned projects that are still using Engine V1 after July 1st? Will they remain accessible in the Editor, or will they be archived/locked?
Also, will users still be able to open those projects later and manually switch them to Engine V2 in Project Settings, or does the migration need to be done before July 1st?
They will not be archived or locked just because they are still using Engine V1.
After July 1st, those projects will still be accessible in the Editor, but the Editor will open them using Engine V2. The Engine V1 Editor fallback will no longer be available, and the Engine V1/Engine V2 switch option will be removed.
Users do not need to migrate before July 1st to preserve access to their projects, but active projects should be tested before then so any Engine V2 differences can be addressed ahead of time.
Existing published builds are not changed by this update.
My name is Martin Brignone. I understand that on July 1st the option to export using Engine 1.0 will be removed from the editor.
I would like to ask if there is any possibility of extending this deadline for my company for a little longer (perhaps 2–3 additional months). We still have several active client projects that rely on Engine 1.0, and unfortunately, we do not have a realistic way to migrate all of them immediately.
Many of these are existing client projects where clients occasionally request only small updates or minor fixes. In those cases, migrating an entire project to a newer engine version is not feasible at the moment just to implement a small change. However, we still need access to make those small updates, which happen approximately once per month.
Would it be possible to keep some form of editor access available for Engine 1.0, or provide a dedicated editor link for legacy projects? I am not asking for continued maintenance or support from your side — I fully understand that Engine 1.0 will no longer receive updates or bug fixes. I only need the ability to make small changes to existing projects under my own responsibility.
I would really appreciate if you could consider giving us this possibility.
I’m not a casual customer — I’ve been working with PlayCanvas for 8 years and currently maintain 4 active accounts.
Thank you for your time and consideration.
Best regards,
Martin Brignone
Thank you for the detailed message, and for your many years working with PlayCanvas. We appreciate that long-running client projects can still require small updates from time to time.
Unfortunately, we won’t be extending the July 1st deadline or providing a dedicated Engine V1 Editor link. The Engine V1 Editor fallback has already remained available for a long migration period, and keeping it open would still mean maintaining a separate Editor/runtime path.
To clarify the available options:
Existing published PlayCanvas builds are not affected and will continue to serve their current version.
Any new update published through the Editor or PlayCanvas Hosting after July 1st will need to use Engine V2.
If a project must stay on Engine V1 for now, we recommend downloading a known-good build before July 1st. The Vite download option can help with faster local iteration on exported builds, but that workflow is outside PlayCanvas Hosting and Editor publishing.
For projects that need ongoing Editor or PlayCanvas Hosting updates, the path is migration to Engine V2.
The User Manual includes docs for Engine compatibility, Engine V1 to V2 migration, and scripting migration. The Asset Auditor in the Editor can also help identify common migration issues, especially around sRGB texture settings and visual differences. The PlayCanvas VS Code extension may also help with script migration by mirroring text assets locally and working well with source control, type checking, and AI-assisted review.
If you hit specific Engine V2 migration blockers, please share details, screenshots, console output, or a minimal repro. We can look at concrete migration issues, but we can’t keep the Engine V1 Editor fallback open past the deadline.