Two numbers dominate every VR video listing, and most people read them as a ranking: 360° sounds like more than 180°, so a 360° scene must be the better one. It is not a ranking. Both numbers describe a field of view — how much of the sphere around the camera was recorded — and the wider one buys that coverage with the only two currencies a video file has: pixels and depth.
Every scene we shoot is 180° equirectangular and stereoscopic, side by side, up to native 8K. That is a decision rather than a shortfall, and this page makes the case for it without pretending 360° has no purpose. It does. It is simply a different tool, and it is almost never the one that makes a scene feel like you are in the room.
What the two numbers actually mean
180° is the front hemisphere. The camera records everything in front of it, shoulder to shoulder and floor to ceiling, from one fixed vantage point. Two lenses sit roughly a human eye-width apart and point the same way, so each of your eyes receives its own image of the same scene. You can look up, down and to either side; the recorded field runs out only when you turn far enough to look behind you.
360° is the whole sphere. Several lenses face outward in every direction and their images are stitched into one frame. Nothing is missing — which also means nothing is hidden. What typically sits behind a camera on a set is lighting, the rig’s own stand, the crew, and the seam where two lenses were joined into a patch of wall. The “look behind you” promise is real; the question is whether what is behind you was worth what it cost to record.
Where the pixels go
A VR resolution label almost always describes the whole packed frame — both eyes stored side by side in one image — and each eye’s half is then stretched across the recorded field. Our VR resolution guide runs that arithmetic in full. The short version, per eye, across 180°:
- 4K — 1920 pixels per eye
- 5K — 2560 per eye
- 7K — 3360 per eye
- 8K — 4096 per eye; our masters are 8192 × 4096 packed frames
Spread 1920 pixels across 180° and you get about 10.7 pixels per degree. That single figure is behind every “why does 4K look soft in a headset” complaint, and it is the reason the 8K tier exists at all.
Now take an identical file and spread it across 360° instead. The same 1920 pixels per eye cover twice the arc, so every degree gets half the detail: roughly 5.3 pixels per degree. The download is the same size, the label on it is the same, and the image is half as sharp wherever you happen to be looking.
Follow that through and the marketing collapses into arithmetic. An 8K 360° file puts about 4096 pixels per eye across 360° — approximately 11.4 pixels per degree, which is roughly what a plain 4K 180° file already gives you. A 360° file has to carry the 8K label just to match what a 4K 180° file already delivers. That is why 8K 360° files so rarely look like 8K. The pixels are real; they are spread twice as thin.
It gets one step worse in practice. A headset does not show you the whole recorded field at once — current hardware displays a window of roughly 100° to 110° and you turn your head for the rest. In a 180° file, well over half of each eye’s pixels are on the panel at any given moment. In a 360° file it is under a third, and the remainder is detail you paid to download so that it could sit behind your head.
Stereo depth: the difference that actually matters
Pixels are the argument people have. Depth is the one that decides how a scene feels, and it is where the two formats genuinely separate.
A 180° rig has one job: two lenses, one eye-width apart, pointed the same way. Every part of the recorded field is captured twice from slightly different positions, which is exactly what your visual system needs in order to build a sense of distance. Nothing has to be reconciled afterwards, because no other direction is competing for the same lenses.
A 360° rig cannot do that everywhere at once. True stereo in every direction means every direction needs its own correctly spaced pair, and all of those pairs have to be stitched into a single sphere. Most 360° material therefore arrives monoscopic — one flat image shown to both eyes — or stereoscopic with compromises that show up where the lenses overlap and near the poles, straight up and straight down.
Mono is where the illusion quietly dies. You can still turn your head, and the world still surrounds you, but nothing in it has volume. A body an arm’s length away and the wall behind it sit on the same invisible plane. Presence in VR video comes from depth far more than from coverage, which is why studios shooting for presence shoot 180°: it spends everything the format has on the part of the sphere you are facing.
What 360° is genuinely good for
There is real work that 360° does better, and it deserves naming rather than dismissing. Anything where the space is the subject: a room you want to survey, a venue, a landscape, an event happening around you, documentary and travel footage where looking the wrong way is part of the experience. If the point is that you choose where to look, 360° is the honest format for it.
It also suits pieces where the camera travels, because a wider field keeps the world coherent while the vantage point changes. The closest thing we shoot is our moving camera category — still 180° and still fully stereoscopic, but with the camera in motion rather than locked down. If framing is what you are after instead, POV puts you in the scene and non-POV keeps you as an observer in the room.
And to be plain about it: if you came here searching for 360° VR downloads, we do not have them. We shoot no 360° masters and no fisheye masters. What you get instead is 8K VR porn captured natively at 180° in true side-by-side stereo, and the ability to download VR porn videos at full bitrate from any scene page — our download guide covers getting them into the headset.
Setting your player for each
Field of view is a player setting, and getting it wrong produces symptoms people mistake for bad video. Every serious player exposes the same two controls under some name: projection type and stereoscopic mode.
For our files, and for any 180° stereoscopic scene:
- Projection: equirectangular, at 180°.
- Stereoscopic mode: left-right, the side-by-side layout.
- Leave the lens presets alone. They exist for fisheye masters, and we publish none.
For a 360° file from somewhere else:
- Projection: equirectangular, at 360°.
- Stereoscopic mode: mono, unless the file is explicitly labelled as 3D — then left-right or top-bottom, as labelled.
- If a 360° file plays as two half-width copies of the same image, the stereo mode is set for a stereoscopic file that this one is not.
The tell for a projection mismatch is geometry rather than sharpness. If the world stretches at the edges while the centre looks squeezed, a 180° file is being played as 360°. If the scene wraps too tightly and the image meets itself behind you, a 360° file is being played as 180°. Our HereSphere settings guide walks through the values one by one, and the player comparison covers which app to use in the first place.
So which should you pick?
- Presence, detail and real depth — 180°, every time. The pixels and the stereo both land where you are looking.
- Exploring a place, or an event happening around you — 360°, and take the softer image as the price of coverage.
- Your headset is not the variable. Quest, PICO and Vision Pro have players that handle both formats, and so does a PC-connected PSVR2; what differs is the file.
- If the complaint is sharpness, it is a resolution question rather than a field-of-view one — the resolution guide has the numbers.
The short answer
180° is not the smaller format. It is the one that spends every pixel and every bit of stereo depth on the part of the sphere you are facing, which is the part that decides whether a scene reads as being there or as watching a screen. SexBabesVR shoots over 700 exclusive scenes that way — native 8K, 180° equirectangular, true side-by-side stereo, with downloads and a “Watch in your VR headset” bar on every scene page.