Nintendo Switch 2 Development - What We Know About the Next Console

Nintendo's successor to the Switch is one of the most anticipated platforms for indie and mid-size studios. Whether you are already targeting the current Switch or planning your first Nintendo release, understanding what we know so far about Switch 2 development can help you plan your pipeline and outreach. This post rounds up reported specs, dev kit access, and practical steps you can take now.

Image: Hulkamania! by Dribbble Artist

Why Switch 2 Matters for Game Developers

The original Switch proved that a hybrid handheld can support both indie hits and major franchises. A successor with better performance and modern features could extend that ecosystem for years. For developers, that means a large installed base, a storefront that still highlights smaller titles, and an audience that buys a wide variety of genres. Getting ahead of hardware and tooling rumors helps you decide when to apply for dev access and how to structure your next project.

Reported Hardware and Features

Details are still unofficial, but multiple reports and leaks have pointed to a consistent direction. Treat the following as a summary of what has been discussed in the press and by analysts, not as confirmed specs.

Display and Resolution

• Handheld: A larger LCD screen with support for up to 1080p and higher refresh rates (e.g. 120 Hz in some reports).
• Docked: 4K output at 60 Hz, with some reports suggesting 1440p at higher frame rates in certain configurations.
• HDR: HDR support has been mentioned for both the built-in display and compatible TVs.

These targets suggest you will be able to ship a single build that scales from handheld to docked, similar to the current Switch but with higher ceilings. Planning for 1080p handheld and 4K docked (with scaling) is a reasonable mental model.

DLSS and Upscaling

NVIDIA DLSS (with versions such as 3.1 mentioned in leaks) has been widely reported for the new device. That implies:

• Better image quality at lower native resolutions.
• Potential for higher frame rates when using upscaling.
• A pipeline that benefits from supporting dynamic resolution and DLSS-friendly settings.

If you use Unreal or Unity, keeping an eye on official Nintendo and engine support for DLSS on Switch 2 will be important once SDKs and documentation are available.

Controllers and Input

Reports have mentioned updated Joy-Con-style controllers (sometimes referred to as Joy-Con 2) with additional buttons (e.g. a “C” button) and features such as mouse mode for certain use cases. Multiplayer and sharing features (e.g. GameShare) have also been mentioned. For now, the takeaway is to expect an evolution of the current input model rather than a complete break, so existing Switch input patterns will likely still apply.

Dev Kit Access and Distribution

Nintendo has historically been selective with dev kit distribution, and that appears to remain true for Switch 2.

Who Is Getting Kits

Multiple outlets have reported that Nintendo is prioritizing established, reliable partners. That often means:

• Studios that already have a track record on Switch or other Nintendo platforms.
• Teams that can demonstrate a clear plan for their title and how it uses the new hardware.

Smaller or first-time Nintendo developers have reported waiting longer or not yet having access. If you are in that group, you are not alone; many teams are in the same situation.

How to Improve Your Chances

• Apply through official channels. Use Nintendo’s developer portal and any published process for applying for dev kit access. Keep your studio and project information up to date.
• Show a concrete plan. Be ready to explain your game, target audience, and how you intend to use Switch 2 features (e.g. resolution, performance, input).
• Stability matters. Nintendo has been reported to consider organizational stability when approving partners. If your company has had recent layoffs or restructuring, that may be a factor.

Pro Tip: If you are not yet approved, continue developing on Switch (or on a scalable engine setup). Many engines let you target “console-like” settings (resolution, frame rate, effects) so that when you do get a kit, porting is smoother.

What You Can Do Now Without a Dev Kit

You do not need a Switch 2 kit in hand to prepare.

Engine and Project Setup

• Unreal and Unity: Follow Nintendo’s official pages and partner programs. When Switch 2 support is announced, upgrade when it makes sense for your schedule.
• Resolution and scaling: Design for variable resolution and multiple performance tiers. This will help you when you need to support both handheld and docked profiles.
• Input: Keep input logic abstract (actions rather than raw buttons) so you can map to new controller layouts later.

Content and Art Pipeline

• Assets: Keep assets flexible. Avoid baking in assumptions that only work on current Switch; scalable LODs and resolution-friendly art will transfer better.
• Performance: Profile and optimize on current Switch or on PC with similar constraints. Good habits (draw calls, memory, load times) will carry over.

Business and Publishing

• Publishing agreements: If you already have a Nintendo publisher or partner agreement, stay in contact and ask about Switch 2 timelines when appropriate.
• Roadmap: Plan milestones so that a later dev kit arrival can be integrated without derailing your entire schedule.

Common Questions

When will Switch 2 be released?
Nintendo has not announced an official release date in our sources. Reports and speculation vary. Focus on what you can control: applying for access, keeping your project portable, and following official Nintendo and engine announcements.

Do I need to learn a new programming language or API?
Until Nintendo and engine vendors announce Switch 2 support, assume that existing C++/C# and engine APIs will extend to the new hardware, possibly with new configuration and feature flags. Watch for official SDK and engine release notes.

Should I delay my current Switch game for Switch 2?
Unless you have a specific strategic reason (e.g. a sequel planned for launch), shipping and supporting a current Switch title usually remains valuable. The existing install base is large, and experience with Nintendo’s pipeline will help when you do target Switch 2.

What if I still do not have a dev kit?
Continue building your game with scalable settings and clean architecture. Apply or re-apply through Nintendo’s process, keep your documentation and pitch updated, and use current Switch or PC as your primary target until access is granted.

Summary

Switch 2 looks like an evolution of the Switch concept with better resolution, refresh rates, and features such as DLSS. Dev kit access is selective and skewed toward established partners, but you can still prepare by keeping your engine and project flexible, optimizing for multiple performance tiers, and staying in touch with Nintendo’s developer programs. As official specs and SDK details are announced, update your plan and target settings accordingly.

For more on console and multiplatform development, see our Unreal Engine and Unity guides. Found this useful? Bookmark it and share it with your team when discussing your Switch 2 roadmap.