> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt
> Use this file to discover all available pages before exploring further.
# XVC packages
> Upload GDK-generated XVC packages for XBOX consoles in Partner Center, including EKB, ContentId, layout files, submission validator logs, and symbols.
XVC packages are special types of packages that can run only on XBOX console devices. These are created with the [Game Development Kit (GDK)](https://learn.microsoft.com/en-us/gaming/gdk).
To use the GDK to create games for XBOX consoles, you must be a managed Creator with Microsoft. For more information, see [Onboarding](/publishing/game-publishing/publishing-processes/managed-creators/publishing-processes-onboarding-new-creator).
## Upload XVC packages
If you have the proper permissions, you can upload XVC packages through the **Packages** page in Partner Center, as you would upload any other packages. However, after you upload an XVC package, a new section will appear for additional file uploads and other details of the package.
* The **EKB** (Encryption Key Blob) is the file used to encrypt the XVC package. The file is generated when you create an XVC package. To upload this file, select **Upload EKB**. After uploading the file, you can switch it out by selecting **Change EKB**. If the EKB isn't provided, the XVC file upload will stop processing.
* The **ContentId** is the GUID (Globally Unique Identifier) that identifies the package and is the same for each version of that package.
* If the XVC package will be distributed on physical discs and will require multiple discs or will use intelligent delivery, you'll need to supply a **Layout file**. This file describes where the game files will be located on the discs, as well as the specific chunks to be downloaded for the customer's hardware and locale. To upload a Layout file, select **Upload layout file**. After uploading it, you can switch it out by selecting **Change layout file**.
* The **Submission Validator** log file is created during the packaging process, if you have the Submission Validator tool installed with the GDK. For more information, see [Submission Validator](#submission-validator) in this topic.
* A **Symbols** zip folder can be uploaded to enable detailed crash data in your game's health report. For more information, see [Symbols](#symbols) in this topic.
Layout.xml provides detail about the layout of your package. This is different from a disc layout file that provides information about how the package should be configured when discs are created. Don't upload the layout.xml file to the disc layout.
If you need to remove a package, select **Remove**. Note that if you remove a package in error, it must be reuploaded or imported from another branch if available.
### Submission Validator
For each XVC package you submit for certification, you'll have to supply a Submission Validator log file. Failure to include this file will delay certification. The log file will be generated by the Submission Validator tool during the makepkg process, if a valid version of the tool is installed with the GDK. You should always use the most recent version of Submission Validator when building packages. Download the latest version of Submission Validator from [Game Development Resources | Microsoft Game Dev](https://developer.microsoft.com/en-us/games/resources/). For more information about changes in the latest Submission Validator release, see [Submission Validator Updates](https://aka.ms/subvalupdates).
Before uploading your package to Partner Center, we strongly recommend opening the Submission Validator log file and reviewing any elements marked as **warning** or **failure**. Any failures or unexpected warnings must be resolved before submitting the package for Certification or the submission will be failed.
### Symbols
To enable us to show you detailed crash data in the [Health report](https://learn.microsoft.com/windows/apps/publish/health-report), you'll need to supply a **Symbols file**. Detailed crash data consists of the number of failure hits over the last month, as well as of a failure log that lists details of occurrences: date, package version, device type, device model, OS build, and more. The Symbols file must be in .zip format and should contain a .pdb file for successful indexing of symbols. The zip folder might be generated automatically during the package creation process. To upload the Symbols file, select **Upload symbols file**. After uploading the file, you can switch it out by selecting **Change symbols file**.
## Reviewing package properties
To see more properties of the XVC package, select **Show details**:
* **XvcProductId** is analogous to the **Product Id** for a product instance. This value is generated by Partner Center when the XVC package is ingested.
* **Red Package** is the version of the XVC package that can run only on development consoles. This version is created when you publish the product to a development sandbox.
* **Green Package** is the version that can run only on retail consoles. This version is created when you publish to the CERT or RETAIL sandboxes.
For information on XVC packages, EKBs, and layout files, see the [Overview of packaging](https://learn.microsoft.com/en-us/gaming/gdk/_content/gc/packaging/overviews/packaging).
## Next steps
## See also
* [Review and Publish](/publishing/game-publishing/concepts/modular-submission)
* [Health report](https://learn.microsoft.com/windows/apps/publish/health-report)
## Related topics
- [Packages](/publishing/game-publishing/concepts/game-package-management.md)
- [How to configure package flights for game packages](/publishing/game-publishing/how-to/how-to-package-flights-for-xvc-packages.md)
- [Advanced settings for packages](/publishing/game-publishing/how-to/how-to-manage-advanced-settings-for-packages.md)
- [XPackageKind](/reference/system/xpackage/enums/xpackagekind.md)
- [Create a game package and upload it in Partner Center](/publishing/game-publishing/tutorial-xbox-managed/how-to-create-a-package.md)