Assets are the user-facing images, titles, covers, screenshots, and trailers of your app that can be used to market your app to users. It is important that every asset highlights the elements that make your app unique and appealing to the target audience. The review team looks at assets as part of the publishing review process.
Note: We do not review your assets for IP infringement. It is your responsibility to ensure you have obtained all the rights necessary to the content you provide to us.
Your assets must adhere to the following guidelines for your app to pass the publishing review process:
Branded assets are images that include your title text and are the first images of your apps that users will see when browsing the Meta Horizon Store or the Link PC VR Store (formerly the Rift Store). These are the most important visuals to engage our users. Clean, simple, and easy-to-read branded assets are crucial to leaving a long-lasting impression. Users can see these assets in the Meta Horizon mobile app, the web store, and the headset.
Your branded assets must be consistent with each other across your app and contain the same imagery across all surfaces. (Surfaces include the web, VR, and the mobile app.) Users need to be able to easily identify the title of your app with a quick glance at the assets, much like identifying a book cover from a thumbnail image in a catalog. To do this, the style and size of your title-text should be prominent and in a contrasting color and font to differentiate it from the background.
Additionally, titles and key focal points need to be placed in a safe area of the asset so that they won’t be obscured or cut off when viewed on various surfaces or devices. Templates that show where the safe area is on an asset can be downloaded to make this clear. For more information, see Safe areas.
Make sure your branded assets cover the following requirements:
Exact Title Match - Assets must have the exact title of the app on them for approvals, with the exception of the icon. The title of your experience must match the title in your assets.
Titles and key focal points placed in the safe area - This to ensure that the important parts of your asset are not cut off on various surfaces or devices.
Clear legibility across all surfaces - Users should be able to easily identify the title of your experience with a glance at your assets. The style and size of your title-text should be prominent.
Contrast from background - Do not have your title-text blend in with the background. Find a style for your colors and fonts that provides enough contrast to be clearly legible to users.
Consistency - Your branded assets must be consistent with each other and contain the same imagery across all surfaces. This ensures that users always identify your experience across multiple surfaces.
Scalability - Your branded assets will appear to users in different sizes on different surfaces. Keep scaling in mind when designing the visual elements of your asset.
Don’t add badges or banners to your branded asset images.
Don’t add generic superlatives, vague update text, unattributed quotes, or pricing information to your branded assets.
Don’t place text in the corners of the branded asset images.
Don’t add taglines or descriptive words to your branded asset.
No other text should be bigger or more prominent than the title. Your title-text is the most important text for users.
For Meta Quest devices, don’t reference non-Meta Quest hardware and platforms in your assets.
The following are recommended:
Keep it simple. Clean and easy to read assets are easier for users to understand and identify your brand.
Make sure your title-text is large and clearly legible.
Keep all of your branded assets consistent; they must share key elements.
Bring out the most exciting parts of your experience by using key-characters, scenes, and objects in your images.
Keep the title-text and logos in the safe areas.
Avoid using “VR” in your title. VR is a great descriptive word for everything outside of Meta Quest. Once you’re here, it’s redundant.
Test your assets before launch. It’s important to get an idea of what users think your assets communicate rather than just relying on what you think it does.
Before creating your assets, try to sum up your experience in a few words. This will help make sure your assets communicate that idea consistently.
Examples of branded asset design
An engaging branded asset promotes the most visually descriptive elements of your experience, while balancing the placement of a title or logo.
Bad examples
The following two designs would not pass review:
In this example, the fire in the background makes the title hard to read.
This example has poor clarity, and the title is in the bleed area.
Good examples
The following are examples of well-done branded assets from currently available titles:
The assets in this example are colorful, expressive, and legible at any size.
In this example, the key focal points are in the safe area and have great contrast.
It’s important to consider that branded assets will be resized and surrounded by many other apps in the Store. Because they are used to identify your experience at the top level, it is crucial that they have similar and consistent design and are easy to identify.
One particular asset may appear on different surfaces, resized and repositioned.
Branded asset specifications
Branded assets establish your brand and help users identify your product across all Meta platforms and surfaces. Meta requires that assets be similar and consistent for maximum impact and clarity. Here are the aspect ratio, resolution, and format requirements for branded assets:
Asset Name
Aspect Ratio
Resolution (width x height)
Image Format
Hero Cover
10:3
3000x900px
32-bit PNG
Cover Landscape
16:9
2560x1440px
32-bit PNG
Cover Square
1:1
1440x1440px
32-bit PNG
Cover Portrait
7:10
1008x1440px
32-bit PNG
Mini Landscape
3:1
1080x360px
32-bit PNG
Logo (Transparent)
Variable
9000x1440px (max size)
32-bit PNG (transparent)
Icon
1:1
512x512px
32-bit PNG
Screenshots
16:9
2560x1440px
32-bit PNG
Trailer
16:9
1080p (min) 2k (max)
MP4/H.264/AAC
Trailer Cover Image
16:9
2560x1440px
32-bit PNG
360 Preview (Cubestrip format) (Equirect format)
6:1 2:1
12288x2048px 7680x3840px
32-bit PNG, JPEG, KTX 32-bit PNG, JPEG, KTX
Safe areas
Branded assets appear on a variety of surfaces in a number of ways. To ensure that your title-text and key focus points are clearly visible on all surfaces and aren’t cut off or obscured, these must be within a safe area on the asset. Non-essential images can be located outside the safe area, in the bleed area, but items in the bleed area could potentially be cut off or obscured on some surfaces. Additionally, all versions of the assets must be consistent with each other.
Whether your asset is displayed on your Product Detail page (PDP) in VR or a category section on the mobile app, we want to ensure that your asset looks its best.
Hero cover
The Hero cover is the main asset on your PDP. Because this page is where users choose your app (or don’t), it needs to make the best impression.
The title must be in the safe area (the focal point). The bleed areas should contain less important parts of your cover, as they may get cropped or we might add pre-set information from our UI. Remember, the title-text on the hero cover image must match the title of your experience.
The Hero cover requires the following:
It must be the same design as your Cover assets (below)
32-bit PNG format.
Cover assets
Cover assets come in three varieties (square, portrait, landscape) and are the most frequently viewed marketing content for your experience. They may be displayed in web browsers, mobile and PC clients, in the headset, and other places at various sizes.
Note the design consistency. The images are not identical, but have the same design elements in similar positions.
Cover assets require the following:
All assets must be similar and consistent
Their design must be reflected in the Hero cover (above)
32-bit PNG format.
Logo (transparent)
The logo allows your audience to quickly recognize your experience. This is your brand.
For Meta Quest devices, It is most often used in-headset, the Meta Horizon Store, library, and your app’s PDP.
Logos must have transparent backgrounds, as they might be subject to different background treatments in VR.
Keep your logo simple and recognizable while maintaining legibility. This logo image must have a transparent background because there may be times when the logo is placed against different backgrounds in VR. Your logo should also be contrast-proof to maintain legibility regardless of the background treatment.
Logos require the following:
Maintain legibility when scaled to various sizes
32-bit PNG format with transparent background
Icon
The icon is primarily used when your app appears on a mobile feed. It’s used for events, destinations, and other mobile feed features. Your icon art needs to maintain legibility across various sizes, so you may have to modify visual elements so that they remain clear as the image is scaled down.
Icons require the following:
It must match your VR experience and not your company
Corners of the icon must be squared, not slanted or rounded
Must be a solid filled asset and must not have any transparencies
32-bit PNG format with dimensions of 512px x 512px
Screenshots
Screenshots help display your app and can help users make the decision to purchase it. Each image you use should represent a unique scene highlighting the best part of the experience.
When creating a screenshot, be sure to have a clear focal point for the image.
The following are required:
Clear, sharp screenshots
5 images
All screenshots must reflect actual in-experience content
We recommend screenshots to be from the gameplay POV
One or two mixed reality or 3rd POV screenshots are allowed
No banners, badges, titles, or marketing text
Branded assets are not allowed as screenshots
Landscape image: 16:9 aspect ratio, 2560 x 1440 px resolution
32-bit PNG format
The following are examples of well-done screenshots from currently available titles:
Raccoon Lagoon - A screenshot that shows off a common gameplay interaction is a solid method to inform a user about what types of actions they will take in your experience.
Dead and Buried II: Reloaded - Screenshots can be of an action shot that shows off some of the wacky weaponry that a player might wield in the experience.
Fail Factory - A screenshot can be an awesome action shot showing off the colorful low-poly environment that the experience offers.
Trailer
A trailer is the supporting 2D video for your experience and is an important part of getting users interested. You’ll want to feature the best highlights of your experience that will make users want to download it.
It can be difficult to convey an immersive VR experience on a video. The trailer you make will be an important part of how potential users understand the content and the breadth of what you are offering. Consider using a mixture of traditional shots, mixed reality, and first person POV shots in your trailer.
Trailers require the following:
MP4/H.264/AAC format
Resolution: minimum 1080p, maximum 2k
Trailer length: 30 seconds minimum to 2 minutes maximum
Graphics and gameplay must be representative of in-experience content
You may start and end with your app logo, but don’t use it throughout
Any hardware shown in your trailer must be the same as the platform your experience is designed for
Only Meta Quest headsets, controllers and hardware are allowed
Trailers must follow Hardware Safety guidelines (wrist straps, play area, etc.)
The trailer cover image is the thumbnail that users see before playing your trailer. You have a number of options for your trailer cover image. Some developers use this image to promote the most visually descriptive frame of the video content. Others use the asset to reinforce brand consistency. Your choices are wide-open.
The trailer cover image requires the following:
Must be between 30 seconds and 2 minutes
Do not include 3rd-party marketing logos
Landscape image: 16:9 aspect ratio, 2560 x 1440 px resolution
32-bit PNG format
360 previews
You can upload your 360° preview as either a cubestrip or an equirectangular projection. Cubestrips provide more effective use of the available pixels and are preferred. There is no need to specify the type of projection, it is detected automatically.
Cubestrip
A 6x1 monoscopic cubestrip provides the highest fidelity 360° previews.
Minimum target dimension: 12288 x 2048 pixels
Face order: left, right, up, down, front, back
Format: JPEG minimum 80 quality, PNG, KTX
Maximum file size: 2.3 MB
Equirectangular projection
A monoscopic equirectangular asset with a 2:1 aspect ratio is also acceptable.
Minimum target dimension: 7680 x 3840 pixels
Format: JPEG minimum 80 quality, PNG, KTX
Maximum file size: 2.3 MB
Safety and Comfort
Don’t position characters in poses that can be perceived as directly threatening users. For example, a monster in a threatening pose directly behind the user is unacceptable.
Maintain a 10 meter minimum distance between the user and content to help prevent confusion and potential injury. Don’t include any characters, props, or environmental objects that could encourage a user to attempt to touch them.
Don’t include weapons, violence, blood, and so on. Exemptions may be granted by request.
Text and Branding
Don’t use title text in the graphic.
Don’t add badges, banners, or awards in the graphic.
Don’t add taglines or descriptive words in the graphic.
Best practices
360° previews deliver on the VR experience users expect. These best practices can help you deliver quality results that match those expectations.
Technical
JPEG compression for the uploaded media should not be lower than 80 quality. Given the 2.3 MB file size limitation, finding the balance between resolution and compression might require you to experiment.
Render in a loss-less graphics format at high resolution and then rescale or convert the graphics to your target dimension and graphics format in post-production instead of rendering directly to the target.
For 6x1 monoscopic cubestrips, consider rendering 2048 x 2048 faces to a high-resolution PNG.
For 2:1 equirectangular graphics, consider rendering to a 8192 x 4096 PNG.
If using Unity, you can use the OVR Screenshot Wizard utility included in the Meta XR Core SDK to create a “Cube Map Screenshot” cubestrip that conforms to the guidelines.
KTX (Khronos Texture) is also an accepted graphics format. If you have the ability to produce KTX version 1.0 textures, a KTX file might yield slightly smaller file sizes compared to JPEG.
Environment
Choose a location that feels unique to your experience and immersive in a way that makes the user feel as if they have been teleported to a new world.
Evoke a strong sense of immersion by utilizing the 360° space to place content in all directions. Creatively explore how to make the most out of the space.
Utilize scale such as large buildings or structures.
The floor height of the camera should be at least 1.56m or 5’6”.
Keep all your branded assets consistent, cohesive, and representative of the app content.
Content updates
An important part of publishing content is what you do post-launch. Many developers decide to add features or content to keep users engaged. A major content update, such as adding a multiplayer mode or providing add on content (AOC) may warrant an update to your branded assets to attract attention from our users. In the event that you have branded asset updates, we recommend you submit a new set of assets with updated or redesigned covers from the base up.
We recommend that branded asset updates be submitted a week or more in advance of your planned content update release.
You should name your content update, but vague extraneous text such as “New Content Update” is not allowed. We strongly suggest a name that is more specific, user-oriented, or dramatic to attract your user’s attention. For example, “Summer of Bullets” is much better than “New Summer Content”.
Content updates require the following:
Your experience title must still be the largest element on the asset
The additional text associated with your content or feature update must be specific
As with all assets, you may not badge your branded assets to reflect sales, company logo, or other information.
The following examples show extra elements that would lead to failure during the publishing review:
Banner and vague text not allowed.
Vague banner in bleed area is not allowed.
However, the following show examples of well done content update assets from titles currently available on the Meta Horizon Store:
