The 2:1 rectangle is not a convention, it is the geometry

Cut a sphere along one meridian and flatten it, and you get a map twice as wide as it is tall. That is the equirectangular projection, and it is what every sphere media player expects: width covers 360 degrees around the equator, height covers 180 degrees from pole to pole. A 3840×1920 file, a 2048×1024 file — the ratio is the point, not the number.

Feed a sphere a 16:9 video and the player either crops it, letterboxes it into a band around the middle, or stretches it and the geometry goes soft. None of those are bugs. The file was the wrong shape.

Where the pixels actually go

Work it out from the pitch. A 2 m sphere at P2.5 has a circumference of about 6.28 m, so roughly 2,513 pixels around the equator. Pole to pole is half that, about 1,256 rows. Which is almost exactly 2:1 — the geometry and the pixel grid agree, and that is why the standard file shape works.

Take the same sphere down to P1.8 and you have about 3,490 pixels around and 1,745 rows. The ratio holds. This is also the number to quote when someone asks what resolution the sphere is: not 4K, but '2,513 × 1,256 around the ball'.

The pole problem, in numbers

At the equator a pixel covers one pitch of width. Twenty degrees from the pole, the circumference is only about a third of the equator, so the same pixel now covers a third of the arc — but it is still one pixel wide on screen, which means the content there is compressed threefold. At the pole itself, every column of the image collapses into a single point.

That is why a logo placed near the top looks squashed and shimmery, and why a face near the pole reads as a smear. Nothing is broken; you are drawing a rectangle onto a shape that has run out of room.

Design rules that survive the curve

Keep anything that has to be readable within about 60 degrees of the equator — that is the band where the distortion stays under roughly 2× and text still resolves. Put a solid colour, a gradient or an abstract field at the poles. If the design needs a globe, accept that the polar caps will be white ice and design them as flat colour.

Second rule: horizontal lines stay horizontal, vertical lines converge. A border or a frame around the map will bend into a curve on the ball, which is usually what you want — but a straight border drawn on the flat file will look like a sagging rope.

Motion is friendlier than detail

Rotation hides the projection. A slow spin, a travelling wave, a colour gradient moving across the surface — these read as a sphere doing something, and nobody notices the poles because nothing at the poles needs to be legible. Detailed static artwork is where spheres look worst, because the eye goes straight to the compressed area.

If the brief is a product image or a menu, put it in the equatorial band as a band — a 360-degree strip with a fixed height, top and bottom in flat colour. That is a legitimate design and it is what most retail spheres actually run.

One file, or a media server doing the warp

Two ways to drive it. Simple: export the 2:1 video and let the player map it, which works on any controller and is what we recommend for a single sphere. Complex: send a normal video to a media server that warps it live, which lets you reuse one asset across a sphere, a ring and a wall at once.

The second costs more and adds a box that can fail. For one sphere in a lobby, the plain 2:1 file is the right answer and the client's designer can produce it in any editing tool with a 2:1 sequence setting.

What to hand the designer

Canvas 2:1 at the real pixel count or a clean multiple of it — on a P2.5 two-metre sphere, 2560×1280 is a good working size. Safe band marked: 60 degrees either side of the equator. Overlay template showing where the seam falls, so the join lands somewhere harmless.

Do those three and the file will play correctly on the first try. Skip them and you get a beautiful 16:9 video, a stretched ball, and a phone call about why the logo looks like it melted.