Meta Horizon Store asset design guidelines

• Cropping tool: Automatically crop images that don’t meet the requirement to focus on the most important content
• Asset library: Reuse previously uploaded images across different asset types, with automatic filtering based on compatibility
• Expand with AI: Automatically expand images to the required dimensions using AI to generate additional background content while preserving your original image

• Meta Horizon Store marketing materials guidelines
• Bleed Area Template files (download)⁠
• Meta Quest Brand Guidelines
• Meta Quest Hardware Safety Guidelines⁠

• Policy Adherence - Branded assets must comply with all Meta Policies and App Policies.
• 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.

• 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.

In this example, the fire in the background makes the title hard to read.

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.

One particular asset may appear on different surfaces, resized and repositioned.

One particular asset may appear on different surfaces, resized and repositioned.

• It must be the same design as your Cover assets (below)
• 24-bit PNG format.

Note the design consistency. The images are not identical, but have the same design elements in similar positions.

• All assets must be similar and consistent
• Their design must be reflected in the Hero cover (above)
• 24-bit PNG format.

• Maintain legibility when scaled to various sizes
• 32-bit PNG format with transparent background

• 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
• 24-bit PNG format with dimensions of 512px x 512px

• Clear, sharp screenshots
• 5 images (no duplicates)
• 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
• 24-bit PNG format

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.

• 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.)
• Any use of the Meta logo should follow the Meta Brand resources and guidelines⁠
• No logos from other platforms
• The trailer must adhere to the Content Guidelines

• 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
• 24-bit PNG format

• 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

• Minimum target dimension: 7680 x 3840 pixels
• Format: JPEG minimum 80 quality, PNG, KTX
• Maximum file size: 2.3 MB

• 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.

• 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.

• 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.

• 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.67m or 5’6”.
• Keep all your branded assets consistent, cohesive, and representative of the app content.

• 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”.

• 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.

Banner and vague text not allowed.

Named content update, main title still the focus.

Great use of color to make the asset fresh.