TL;DR
Unity AI Assistant can generate a cubemap from a text prompt via Create > Rendering > Generate Cubemap, and it outputs an equirectangular asset you assign as a skybox. It works well, but every generation spends Unity AI points. If you only need a skybox — not a full in-editor AI workflow — you can produce the same engine-ready result for free: generate a 2:1 equirectangular panorama in the browser, then convert it to six cube faces labeled to match whichever workflow you're using.
What Unity AI Assistant's Generate Cubemap actually does
Unity's AI Assistant, reached through Create > Rendering > Generate Cubemap, is a text-to-image generation feature, not a format converter. You type a prompt describing the environment you want — "a moody alien canyon at dusk," for instance — and optionally add a negative prompt to steer the model away from artifacts or elements you don't want in the scene. You then pick a model style, such as Cinematic or Cartoon, and a count slider lets you generate several variations in one pass so you can compare results before committing to one. Once you land on a result you like, Unity assigns it directly as a Cubemap asset ready to drop into a Skybox material. Generating a cubemap this way consumes Unity AI points.
Why the output is equirectangular, not six files
Despite the menu item being labeled "Generate Cubemap," the asset Unity actually produces is equirectangular — a single 2:1 panoramic image, not six separate cube faces. That isn't a naming inconsistency; it's a sensible choice of intermediate format. Generative image models are trained and run on flat 2D images, and a 360°×180° environment maps naturally onto one rectangular canvas long before anyone talks about cube faces — equirectangular lets a single generated image describe a full sphere without committing to any particular engine's face layout. This "equirectangular first" approach isn't unique to Unity's AI feature, either: 360° photography and CG environment maps have used the same flat-first convention since long before any AI tooling existed. That's exactly why a standalone equirectangular-to-cubemap conversion step has remained a persistent, recurring need across the industry, regardless of what generated the source image.
The free alternative: generate, then convert
If your actual requirement is "I need a skybox," not "I need Unity's in-editor AI panel specifically," you can get the same equirectangular-then-cubemap pipeline without spending a single AI point. Start at the Skybox Generator: describe your scene in plain language, and it produces a seamless 2:1 equirectangular panorama in your browser, with no install and no per-generation credit meter ticking down while you refine your prompt. Once you have a panorama you're happy with, run it through the Cubemap Generator, which slices the equirectangular image into six square faces and packages them with the naming convention that matches your target engine's workflow. The whole pipeline runs client-side — nothing you generate is uploaded to a server between the two steps. For a solo developer or a small team prototyping skybox variations, this produces functionally the same asset Unity's AI feature does, minus the point cost, with more room to iterate freely before you commit anything to your project. Because the panorama step and the conversion step are separate, you can also keep the equirectangular source around after you've built the cubemap — useful if you later need the same environment for a viewer, a different engine, or a second platform that expects 2:1 input instead of six faces.
Getting the face names right for Unity
Whichever tool produces your six faces, naming them correctly is the step most likely to go wrong — even though Unity itself doesn't strictly enforce any naming scheme. Unity's 6-Sided Skybox material assigns its six textures through six Inspector slots, so you can wire up whatever files you have by hand. Unreal doesn't enter into this at all: it has no official path for importing six loose face images, so an Unreal user should skip the face conversion entirely and import the equirectangular source directly — UE unwraps a 2:1 .hdr into a TextureCube on import, ready for HDRI Backdrop or a skysphere material. What you're really following are community and tool-chain conventions that make batch export and reuse practical. px, nx, py, ny, pz, nz — positive and negative X, Y, and Z, mapped to right, left, up, down, front, and back — is the form common in Unity and Three.js workflows. right, left, top, bottom, front, back is the form most standalone converter tools and older skybox asset packs use, where front means the center of the panorama and right the quarter-turn to its right. Unity adds a twist of its own on top: the six slots on a Skybox/6 Sided material are labelled Front [+Z], Back [-Z], Left [+X], Right [-X], Up [+Y], Down [-Y] — and the slot Unity calls Left is the +X axis, which is the face on your right when you're facing forward. The Cubemap Generator absorbs that for you by naming each exported file after Unity's slot rather than after the axis, so you drop left.png into the Left slot, match every file to the slot with the same name, and never have to reason about the sign of X. Mix two conventions up when you assign faces — say, wire a converter-tool-style set into slots meant for an axis-named layout — and you won't get an error message. You'll get a skybox that renders, but with faces rotated or mirrored relative to each other, producing visible seams or a horizon that doesn't line up at the edges. That failure mode is subtle enough that it often gets misdiagnosed as a texture import setting rather than a mismatched face assignment. The safest habit, regardless of which tool generated the faces, is to load each one individually as a plain texture and confirm its orientation before you assemble the final skybox material — it takes a minute and rules out an entire category of bug. The Cubemap Generator sidesteps most of this by letting you pick the naming convention you want at export time: front/back/left/right/up/down to match Unity's 6-Sided slots by name, px/nx/py/ny/pz/nz for Three.js CubeTextureLoader and most general-purpose tools, or pos_x/neg_x style names for OpenGL-flavoured pipelines.
When Unity AI is still the better choice
None of this makes the free browser path strictly better — it solves a narrower problem well. If you're iterating on a skybox as part of a larger in-editor session — tweaking lighting, checking the result against your scene's fog and post-processing in real time, generating variation after variation without ever leaving Unity — the AI Assistant panel's tight integration is worth the point spend. It also comes with Unity's own support channel and documentation, which matters if you're at a studio that needs an accountable vendor relationship rather than a best-effort community tool. And if your team already has an AI point budget allocated and otherwise unused, spending it on cubemap generation is a reasonable use of a resource you're paying for either way. The browser-based route makes the most sense when cost is the constraint, or when you want a portable equirectangular source image you can reuse across more than one engine — not when in-editor iteration speed is what actually matters to your workflow. Treat the two paths as complementary rather than competing: prototype cheaply outside the editor, then move into Unity's AI panel once you know the direction you're actually iterating toward.
Going the other way: cubemap back to panorama
Sometimes the direction is reversed: you inherit a project with only cube-face textures — no source equirectangular ever saved — and you need to edit the environment as a single panoramic image, or repurpose it for a viewer, a website, or a different engine that expects 2:1 input. Our cubemap to equirectangular converter reassembles the six faces into a single equirectangular image directly in the browser, so you're not stuck with a one-way pipeline — whichever format you start with, you can get to the other.
