All ToolsStart a project ↗
Environment workflow

What cubemap face size should you use?

For a full 2:1 equirectangular panorama, one quarter of its width is a practical starting point for each square cubemap face. A 4096 × 2048 panorama therefore starts at 1024 × 1024 per face. This is a sampling heuristic, not an exact quality equivalence: inspect seams, poles and your final field of view.

From panorama to a testable sizeQuarter-width is a starting heuristic. Validate sampling and orientation in the destination.
  1. 4096 × 2048 sourceA complete 2:1 panorama.
  2. 1024 × 1024 facesStart at 4096 ÷ 4, for six faces.
  3. 6.29 million pixelsInspect seams and poles before increasing size.
The decision

What this solves

Choosing the largest face size increases output and processing but cannot recover detail that was never in the source panorama.

Why width divided by four is only a starting point

A full panorama spans 360 degrees horizontally. A cube face covers a 90-degree direction, so a quarter of the panorama width gives a useful first comparison. The projections distribute samples differently, particularly near face edges and the panorama poles. There is no single conversion ratio that makes every part equally detailed.

For an 8192 × 4096 source, compare 2048-pixel faces first. For a 2048 × 1024 source, start with 512-pixel faces. Increase the size only when the source and destination view show a useful improvement.

Separate size errors from orientation errors

A sharp but rotated horizon usually needs an orientation correction, not more pixels. A discontinuity between faces can result from the face order, an upside-down face, the source seam or filtering. Diagnose these separately.

Use the direction-labelled synthetic panorama linked from the existing conversion workflow. Confirm front, back, left, right, up and down in the receiving viewer before converting a production image. Labels such as px and nx describe axis directions; an application may require a different file naming convention.

Review output rather than the download alone

A set of six images can look correct when opened separately yet show a seam during rotation. Load them into the intended viewer, turn through all four side joins, then look straight up and down. Check with the same texture filtering and field of view used in delivery.

Do not use a screenshot of the tool preview as the final proof. Keep the exported files, destination settings and a short note describing the checks. That lets another artist reproduce the orientation and sampling decision.

A PNG skybox is not an HDR lighting environment

The Labs PNG face workflow is useful for image-based skybox delivery. It must not be described as preserving the radiance of an HDR or EXR lighting source. Display images and lighting environments have different requirements.

If the task is physically based lighting, retain the original high-dynamic-range source and choose an export pipeline that explicitly preserves its numeric range. A larger PNG cannot restore clipped highlights.

Tools for this task

Start with these tools

Use the tools in order, or jump straight to the one that matches the question in front of you.

Workflow

Recommended workflow

The sequence keeps the work practical and reduces the usual guesswork before production.

Inspect the source

Confirm a complete 2:1 panorama with a level horizon and no cropped direction.

Open tool

Choose an initial face size

Start around width divided by four. Compare a smaller and a larger output if the receiving application supports both.

Open tool

Check the destination

Load all six faces with the expected naming and orientation. Inspect every join and both poles.

Open tool
Example outcome

Calculated example: six 1024 × 1024 faces contain 6,291,456 pixels. Six 2048 × 2048 faces contain 25,165,824 pixels, four times as many. At uncompressed RGBA8 those base levels are 24 MiB and 96 MiB respectively, before mipmaps and other allocations.

Basis and limitations

The quarter-width rule is an initial production choice. The pixel counts are arithmetic, not a visual benchmark or an HDR-preservation claim. Original sampling explanation and arithmetic examples. Validate in the receiving application.

XO3D Labs Cube Map Converter: Use the working converter to inspect the chosen face size and export.

XO3D Labs direction-labelled panorama: An original synthetic reference for orientation checks; it contains no HDR lighting data.

Common mistakes
  • Using a cropped panorama as though it covers 360 degrees.
  • Increasing resolution to fix a rotated face.
  • Calling an eight-bit image an HDR lighting source.
Next pages

Keep going

FAQ

Questions this page answers

How many images make a cubemap?

A cubemap uses six square faces. Confirm their order and orientation in the destination viewer.

What face size should I use for a 4K panorama?

For a 4096 × 2048 full panorama, start with 1024 × 1024 faces, then inspect the intended view. This is a heuristic, not a fixed quality rule.

Will larger cubemap faces remove seams?

Not necessarily. Check orientation, source continuity and filtering before increasing resolution.

Next step

Talk to XO3D

Bring the product, audience, launch date and required assets. We can help define the creative direction and production scope from there.

Tell us about your brief

Published by XO3D Labs: 2026-09-17

Updated: 2026-09-17

About the studio behind these tools

XO3D is a director-led product CGI studio, and these tools come out of its own production pipeline rather than being built as marketing. We work with tech, industrial and premium consumer brands on product films, launch stills and interactive experiences.

That makes us the right choice for launch-critical work where the visual standard has to be high and the product may not exist yet.

It makes us the wrong choice for three things: hundreds of routine SKUs to a fixed template, a permanently live self-service configurator across a large range, and the campaign idea itself.