How do I prepare for console certification?

Test against the platform's requirements throughout development, not at the end, especially the platform-specific behaviors (suspend/resume, controller handling, disconnection, account integration) under cert-like conditions, and ensure stability since crashes are common cert failures. Make sure any networking and reporting your game does complies with platform rules, and catch the platform-specific bugs before you submit rather than in a rejected submission.

What Is Console Certification?

Q: What is console certification?

The platform holder's approval process (for PlayStation, Xbox, Nintendo Switch) that a game must pass before release on that console. Each platform has technical and behavioral requirements (TRC, TCR, or lotcheck), and they test your submitted build against them. A game that fails cert cannot ship until the issues are fixed and it is resubmitted.

Q: What does certification check for?

Stability (no crashes or hangs in normal use), correct handling of platform features (controllers, suspend/resume, accounts, storefronts, trophies/achievements), correct behavior in edge cases (disconnection, removed storage, interruptions), and proper use of platform conventions. Many requirements concern behaviors that do not arise on PC, which makes them a common source of cert failures.

Quick answer: Console certification (or 'cert') is the formal review a game must pass to be released on a console platform. Each platform holder, Sony, Microsoft, Nintendo, has a set of technical and behavioral requirements, and they test submitted builds against them. A game that fails cert cannot ship until the issues are fixed and it is resubmitted.

Releasing a game on console is not as simple as uploading it. Each console platform holder requires your game to pass certification, a formal review against their requirements, before it can go on sale. Cert exists to ensure games meet the platform's standards for stability, behavior, and integration, and it is a gate every console game must clear. For developers used to the openness of PC, understanding console certification, and planning for it, is essential to a successful console launch.

What Certification Checks

Certification verifies that your game meets the platform holder's requirements, often called TRC, TCR, or lotcheck depending on the platform. These cover a wide range: stability (the game should not crash or hang in normal use), correct handling of platform features (controllers, suspend/resume, accounts, storefronts, achievements/trophies), correct behavior in edge cases (disconnection, removed storage, system interruptions), proper use of platform terminology and UI conventions, and more. The platform tests your submitted build against this checklist.

Many requirements concern behaviors that do not arise on PC, how the game handles the console being suspended and resumed, what happens when a controller disconnects, correct responses to system-level events. These platform-specific behaviors are a common source of cert issues precisely because they are easy to overlook if you developed primarily on PC.

Why Certification Matters

Certification is a hard gate: fail it, and your game cannot ship on that console until you fix the issues and resubmit, which costs time and can delay your launch. Cert failures are therefore not just bugs but schedule risks, a failed submission can push your release. This makes preparing for cert, and not being surprised by it, important to hitting your console launch date.

Cert also enforces a quality and consistency bar that benefits the platform's ecosystem (and your game): it catches stability and integration problems before players hit them. But it means you must build with the platform's requirements in mind from the start, not bolt compliance on at the end. The platform-specific behaviors cert checks need to be handled in your code well before you submit.

Preparing for Certification

The key to passing cert smoothly is testing against the requirements before you submit, ideally throughout development, not discovering compliance issues at the end. This includes thoroughly testing the platform-specific behaviors (suspend/resume, controller handling, disconnection, account and storefront integration) under cert-like conditions, and ensuring stability, since crashes and hangs are common cert failures.

Any reporting or networking your game does, including bug and crash reporting, must itself comply with the platform's rules (around networking, data, and behavior in restricted states), so plan that in before submission rather than after. Bugnet's crash and bug reporting captures the context to catch the stability and platform-behavior issues that cause cert failures, tagged by build version so you can verify fixes before resubmitting, and supports console builds with capture designed to fit platform constraints. Catching the crashes and platform-specific bugs that fail cert before you submit, rather than in a rejected submission, is what keeps a console launch on schedule.

Console cert is the platform holder's gate every console game must pass. Fail it and you can't ship, so test against the requirements before you submit, not after.