Preparing Submission Packages for Console Certification

Format your final build according to strict technical requirements and submission guidelines mandated by major console platform holders and digital storefronts.

In this lesson, you will learn how to structure and finalize your project’s build artifacts to meet the rigid technical requirements of console platform holders.

When preparing for certification (often called "Submission" or "Gold Master"), moving beyond a simple Shipping build is critical. Platform holders require specific directory structures, metadata files, and package formats that go well beyond the standard .exe or .app output.

The Certification Package Anatomy

A submission package isn't just your game binaries; it is a curated collection of files that allow the platform’s internal "Submission Tool" to validate your project. You must ensure your Project Settings > Packaging is configured to Include Prerequisites, Full Rebuild, and For Distribution.

Crucially, you must handle your Build.cs configurations to strip out non-essential debug symbols while ensuring the Packaging settings align with the console's required "Chunking" strategy. If your game exceeds the initial download size limit for a specific platform, you must partition your data into chunks using Asset Manager settings to ensure the base game remains within the submission threshold.

Example: Customizing the Build Configuration

Before triggering your final build, verify your DefaultGame.ini settings to ensure the packaging process respects platform-specific constraints:

[/Script/UnrealEd.ProjectPackagingSettings]
BuildConfiguration=Shipping
FullRebuild=True
ForDistribution=True
IncludeDebugFiles=False
bCompressed=True
bUseIoStore=True
bGenerateChunks=True

The Validation Workflow

Staged Build: Always build to a "Staged" directory first to verify the file manifest.
Manifest Verification: Use the platform’s proprietary command-line tools to check the AssetRegistry.bin and ensure all dependencies are resolved.
Signing: Apply your platform-specific signing keys (configured in your Provisioning profiles) to the executable.
Submission Tool: Run the platform-provided "App Validation" tool against your staged folder. This will flag issues like missing icons, incorrect splash screens, or unauthorized engine features left active in a shipping build.

By strictly adhering to these requirements, you minimize the risk of "TRC/XR/LCR" (Technical/Xbox/PlayStation Requirement) failures, which are the most common cause for submission rejection.

Key Takeaway: Preparing for submission is a process of curation—ensure your build is stripped of debug data, fully chunked, and signed according to the platform-specific manifest requirements before ever running the submission validation tool.