Unity 7.0 Alpha is now available

Issue Tracker
, ,
1

Hi everyone,

We’re excited to kick off the public Alpha for Unity 7.0 and start sharing weekly builds with you for early testing!

Through the 7.0-alpha tag, you can discuss 7.0 pre-releases with the wider community on Unity Discussions. Our goal in sharing these pre-release versions is to identify and resolve remaining issues, improving overall quality before the official release.

Details

The purpose of the alpha and beta phases is to ensure that everything is working as expected before the developed Unity version is officially released. You can help by sharing your user experiences with us.

If you discover that something is not working as expected, there are some measures you can take to get the issue addressed.

Assess the situation

Primary actions

Secondary actions

  • Was the issue already reported by someone else, but you want to make sure your case will be covered by a fix?
    • Submit a bug report with a minimal reproduction project and respond to requests from Unity personnel.
  • Is there an existing forum topic about the issue?
    • Reply with a description of your case. If not, start a new thread referencing your bug report’s Issue ID.

Guidelines for posting with the 7.0-alpha tag:

  • Reference issue IDs when you start a new topic about a bug. If a bug doesn’t have an ID yet and is unknown, make sure to submit a bug report first before writing about it here.
  • Please discuss separate issues in separate topics and avoid bundling; otherwise, the thread diverges really fast and becomes hard to track. It is OK to start multiple topics consecutively.
  • Please make the effort to ensure that the posted issue is the same as yours before assuming “me too”.
  • Topics that are not clearly related to a 7.0 feature/bug/regression shouldn’t be tagged with 7.0-alpha

If you have any questions or other feedback regarding the pre-release and its features, be it positive or negative, please let us know about it.

Thanks for participating in the alpha!

  1. For Unity 7.0, we’re changing how we ship alpha releases. Instead of one alpha every two weeks, we’ll now ship two alphas per week. This gets the latest changes to you sooner, so you can try new features as they land and check compatibility with your pipelines as Unity 7.0 evolves.

    Because of the faster cadence, we may sometimes skip a build rather than delay it. If we find impactful issues with a build, we’ll skip that release and fix the issues in the next scheduled alpha. With the next one only a few days away, you won’t wait long for updates. Let us know in this thread how the new cadence works for you.

  2. Learn more about where we stand on our path toward .NET modernization as we move closer to the supported release of Unity 6.7LTS and Unity 7.0. in our CoreCLR, Scripting, and .NET Update, October 2026 thread.

26 Likes
Unity 7 is here
Path to CoreCLR, 2026: Upgrade Guide
8

The New Generation of Unity is here :slightly_smiling_face:

5 Likes
11

I’d enjoy hearing from a tester if and how editor iteration improves in 7.0, i.e. domain reloading, editor usability after script modification, etc.

12

When might we have some documentation or discussion about “Temporal Pixel Synthesis” in this release?

13

I see that both Player and Editor Compatibility Levels are still on .NET Standard instead of .NET. Is there an expected time for when .NET full compatibility will be added?

14

Got this from another post.

1 Like
15

This means Domain Reload remains until Beta?

And where is ECS For All? Was it ditched?

4 Likes
16

ECS For All is 7.x

17

Where is this info from? It originally was 6.8 (meaning 7.0)

1 Like
18

Probably not in the alpha period. We’re testing internally and we want to ensure compatibility in the lion’s share of 1st party package/platforms before exposing to users.

1 Like
19

ECS For All is a large initiative spanning multiple architectural changes. We already shipped some of them in earlier 6.x releases (like the EntityId changes) and we’ll continue shipping more of them in 7.0 and beyond. There is no one single release where you should expect to see ‘ECS For All’ on a feature list.

10 Likes
20

By “ECS For All” I mean the main feature - GameObjects as Entities, in the same Hierarchy without SubScenes

9 Likes
22

@mariandev

Thank you for cross posting! You all beat me to these things!

1 Like
23

Not ditched at all :slight_smile: Stay tuned!

Hierarchy without Subscenes (a component of Unified Authoring) will not be in 7.0

6 Likes
24

@Neonage domain reloads are gone. They have been replaced by code reloads and ALC reloading.

We need to change the progress bar notification message…

6 Likes
25

Could we know what can we expect in 7.0 related to ECS for all, and what already in 7.0a0 aside from EntityID and other already in 6.7?

26

@Thaina ,

ECS for all is still in progress and we’ll continue to update everyone as that progress shows up in releases but it will take take time. This is just the first alpha release.

I see you’re already on this other thread as well but that’s the detailed information we can provide at this time in terms of what’s in the alpha and what’s coming. We plan to make updates and releases quickly and continuously from here.

5 Likes