The short answer
To develop for Nintendo Switch 2, a studio registers on the Nintendo Developer Portal and must be approved by Nintendo before it gets platform tools and hardware. Unity supports Switch 2 as an add-on to Unity 6 for approved developers, and Unreal Engine supports Nintendo platforms for approved developers too. Plan for performance work, controls, certification and some lead time for hardware. Studios without approval often work with a partner who already has it.
Step 1: get approved
Nintendo controls access to its platforms. Developers register on the Nintendo Developer Portal and apply. Approval gives access to documentation, tools and the process for obtaining development hardware. Nintendo looks at the company and its plans, and it has been careful about the quality of titles coming to its store.
Step 2: choose your engine path
| Engine | Switch 2 support |
|---|---|
| Unity | Unity announced Switch 2 support as an add-on to Unity 6 for approved Nintendo developers |
| Unreal Engine | Supported for approved Nintendo developers through Epic and Nintendo channels |
| Godot | Console support usually comes through third-party porting companies |
| Custom engine | Possible, with platform SDK access after approval |
Most smaller studios use Unity or Unreal for console projects because platform support and documentation are already in place.
Step 3: plan for hardware lead time
Reports from 2025 and 2026 said some studios waited for development hardware. Build that uncertainty into your schedule: you can do a lot of preparation on PC first, such as controller support, performance budgets and UI scaling, so the console phase is shorter when hardware arrives.
Step 4: the technical work
Performance in two modes
Switch 2 runs docked on a TV and handheld. Games need stable performance in both, usually with different resolution or quality settings. Profile early and often on the real hardware.
Controls
Support Joy-Con and Pro Controller layouts, show correct button prompts, and test that every menu works without touch where touch is not available.
UI and text
Text must be readable on the handheld screen and on a TV across the room. Add text scaling if your game is text-heavy.
Saves, accounts and suspend
Players suspend and resume constantly on a hybrid console. Saves must be robust, and the game must handle sleep and resume cleanly.
Step 5: certification and release
Before release, Nintendo checks games against its technical requirements. Failing certification means fixing issues and resubmitting, which costs time. You also need age ratings for each region and store assets for the eShop. Plan testing time specifically for certification requirements, not just general bug fixing.
Should you port an existing game?
Porting a game that already sells well on PC or mobile is often the lowest-risk way onto Switch 2, because you know the game works and have marketing material. Games that suit handheld play, short sessions and controller input tend to fit best. Our game porting guide covers how ports are scoped and priced.
Working with a partner
A porting or co-development partner with Nintendo approval and console experience can shorten the path, handle certification and avoid common mistakes. Check that the partner has shipped console titles, that you keep ownership of your code, and that the contract covers certification fixes. See how to choose a game development studio.
A realistic timeline
| Phase | What happens |
|---|---|
| Approval | Register on the Developer Portal and wait for Nintendo to approve the company |
| Preparation on PC | Controller support, UI scaling, performance budgets, save handling |
| Hardware and platform setup | Obtain development hardware and set up the engine add-on |
| Porting and optimisation | Get the game running, then tune docked and handheld modes |
| Certification and ratings | Test against requirements, submit, fix and resubmit if needed |
| Launch and patches | Release on the eShop and fix any console-specific issues |
The length of each phase depends heavily on the game, so ask a partner for a phase-by-phase estimate rather than a single number.
Starting the preparation work on PC while approval and hardware are pending is the single best way to shorten the overall schedule, because most controller, UI and save-system work does not need the console at all.
Performance tips for a hybrid console
- Set separate quality presets for docked and handheld play.
- Watch memory closely; console memory budgets are fixed.
- Reduce overdraw and expensive post-processing in handheld mode.
- Keep loading times short, since players often play in short sessions.
- Test battery-heavy scenes for heat and frame-rate drops over long sessions.
Budget items people forget
- Development hardware and test units.
- Certification testing and resubmission time.
- Age ratings in each region.
- eShop assets and localisation.
- Post-launch patches for console-specific issues.
Is Switch 2 worth it for an indie game?
For the right game, yes: Nintendo players buy many games that suit handheld and couch play. But reports also suggest that success on the platform is not automatic for third-party titles, and visibility in the eShop takes marketing effort. Treat Switch 2 as one part of a multi-platform plan rather than the whole strategy.
Sources: Nintendo Developer Portal · Unity: support for developers targeting Nintendo Switch 2 · LevelUp: reports on Switch 2 dev kit access. Checked October 27, 2026.
Related: Co-development · PC game development · Get a quote
Originally published on A Plus Games Studio, a game, AR and VR development studio in Sacramento, CA.
Top comments (0)