# The Plan for React 18

DevFeed: [The Plan for React 18](<https://devfeed.tech/articles/the-plan-for-react-18-22344.md>)

Original publisher: [Read original article](<https://reactjs.org/blog/2021/06/08/the-plan-for-react-18.html>)

Published: 2021-06-08T00:00:00Z

Content type: release

Language: en

Sources: [React](<https://devfeed.tech/sources/react.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [batching](<https://devfeed.tech/tags/batching.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [information](<https://devfeed.tech/tags/information.md>), [react](<https://devfeed.tech/tags/react.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

## AI overview

The React team outlines the plan for React 18, including a Working Group, an Alpha release for library authors, automatic batching, new APIs, and a streaming server renderer. React 18 introduces opt-in concurrent rendering and a gradual upgrade strategy.

## Source excerpt

This blog site has been archived. Go to react.dev/blog to see the recent posts. Update Nov. 15th, 2021 React 18 is now in beta. More information about the status of the release is available in the React 18 Working Group post. The React team is excited to share a few updates: We've started work on the React 18 release, which will be our next major version. We've created a Working Group to prepare the community for gradual adoption of new features in React 18. We've published a React 18 Alpha so that library authors can try it and provide feedback. These updates are primarily aimed at maintainers of third-party libraries. If you're learning, teaching, or using React to build user-facing applications, you can safely ignore this post. But you are welcome to follow the discussions in the React 18 Working Group if you're curious! What's coming in React 18 When it's released, React 18 will include out-of-the-box improvements (like automatic batching), new APIs (like startTransition), and a new streaming server renderer with built-in support for React.lazy. These features are possible thanks to a new opt-in mechanism we're adding in React 18. It's called "concurrent rendering" and it lets React prepare multiple versions of the UI at the same time. This change is mostly behind-the-scenes, but it unlocks new possibilities to improve both real and perceived performance of your app. If you've been following our research into the future of React (we don't expect you to!), you might have heard of something called "concurrent mode" or that it might break your app. In response to this feedback from the community, we've redesigned the upgrade strategy for gradual adoption. Instead of an all-or-nothing "mode", concurrent rendering will only be enabled for updates triggered by one of the new features. In practice, this means you will be able to adopt React 18 without rewrites and try the new features at your own pace. A gradual adoption strategy Since concurrency in React 18 is opt-in