TL;DR
Facebook renders a photo as an interactive 360° sphere only when two conditions hold at once: the image is a 2:1 equirectangular panorama, and the file carries GPano XMP metadata declaring it as one. Miss either and Facebook treats the upload as an ordinary photo — a wide, stretched rectangle with no drag-to-look control.
The overwhelming majority of "Facebook 360 photo not working" cases come down to the second condition. The metadata was there when the camera wrote the file, and an image editor quietly dropped it on save. Test the file before you fix anything — guessing at the cause costs far more time than a ten-second check.
Check your panorama in the 360° Panorama Viewer →
Why Facebook Shows Your 360 Photo as a Flat Image
A 360° photo is not a special file type. It is a normal image whose pixels happen to be laid out in an equirectangular projection, plus a block of XMP metadata that tells any reading application "this is a full sphere, map it accordingly." Strip that metadata and the pixels are untouched — but every app now sees a very wide ordinary photo.
That is exactly what happens in most failure cases. A Ricoh Theta, an Insta360, or any other 360 camera writes the metadata correctly at capture. Then you crop the shot in Photoshop, adjust exposure in Lightroom, run it through a compression service, or pass it through a chat app — and the save path rewrites the file without carrying the GPano block across. Software that faithfully preserves EXIF fields — camera model, date, GPS — doesn't necessarily carry XMP extension namespaces it doesn't recognize. The photo looks identical on disk and is now, as far as Facebook is concerned, flat.
The second common cause is the upload itself. Since Facebook's interface changes around 2020, its handling of 360 uploads has been noticeably stricter. Facebook decides at upload time: the photo either arrives with valid 360 metadata or it is treated as a flat image. Re-uploading the same broken file, or posting it from a different device, does not bring the sphere back.
Quick Test: Is It a Real 360 Photo?
Before touching any metadata tool, find out which of the two conditions is actually broken. Drop the file into the 360° Panorama Viewer — it runs entirely in your browser, with no upload and no account — and read its image check panel. It reports:
- Dimensions and resolution tier, plus whether the aspect ratio matches the 2:1 shape equirectangular requires.
- Whether GPano XMP metadata is present in the file at all.
- File size, so you can sanity-check what your export step actually produced.
Then read the result:
- 2:1 ratio, metadata found → the file itself is fine, so the problem lies elsewhere: a failed upload, a stale cache, or the app you posted from.
- 2:1 ratio, metadata missing → by far the most common case. Go to the metadata sections below.
- Not 2:1 → the pixels themselves are wrong, and no metadata fix will rescue them. See the next section.
The viewer also drops you straight into the sphere, which is a diagnostic in its own right: if the horizon bends or the scene warps as you drag around, it will look just as wrong on Facebook.
The 2:1 Equirectangular Requirement
Equirectangular projection maps longitude to the horizontal axis and latitude to the vertical axis. A full sphere is 360° around and 180° from top to bottom, so a correct panorama is always exactly twice as wide as it is tall: 4096×2048, 5400×2700, 6000×3000. That 2:1 equirectangular aspect ratio is not a stylistic convention — it is what makes the projection arithmetic work.
Feed a non-2:1 image to any 360 renderer and it stretches the picture across the sphere anyway. Faces smear, the horizon tilts, and the zenith and nadir pinch into an unreadable mess. A 3:1 sweep-mode "panorama" from a phone camera is a wide photo, not a sphere, and no amount of metadata editing will turn it into one.
Facebook's upper limit for 360 photos is 6000 × 3000 pixels, so there is nothing to gain from preparing an 8K master for a Facebook post. Export at or below that ceiling and you keep one less resize step in the pipeline.
If your source is an ordinary photo rather than a true spherical capture, the fix is to build a genuine panorama from it. The Photo to 360° Converter takes one to three reference photos and produces a proper 2:1 equirectangular PNG at up to 4K (3840×1920), matching the source lighting and palette. That satisfies the projection condition; the metadata is still a separate step, covered below.
What Is GPano XMP Metadata?
GPano is the XMP namespace Google defined for spherical photos: http://ns.google.com/photos/1.0/panorama/. It lives inside the file's XMP packet, alongside the standard EXIF data, and it is what consumer platforms read to decide whether an image should be opened as a sphere.
The field that carries the decision is:
GPano:ProjectionType = equirectangularThat single tag is the switch. The full GPano spec also defines companion fields that describe the cropped area and the full panorama dimensions, which matter when a capture covers less than the full sphere. For an ordinary full-sphere shot, ProjectionType doing its job is most of the battle.
Google Photos reads the same namespace. That is why a file which works on Facebook usually behaves correctly there too — and why a stripped file breaks in both places at the same time. The metadata is worth repairing in the source file rather than working around it platform by platform.
How to Add 360 Metadata to a Photo
Fastest fix. Start with the 360 Photo Metadata Injector — it runs entirely in your browser, writes the GPano XMP tag without re-encoding the file, and it's free.
Desktop apps. Exif Fixer, a Mac and Windows tool from Keith Martin, is where most 360 shooters end up. It exists specifically to write 360 metadata back into images that lost it. On Windows, Exif Pilot is a general-purpose EXIF editor that can also work on metadata fields directly, which suits you if you are already editing other tags anyway.
Better still, avoid the problem. The cheapest fix is never losing the metadata in the first place. Keep the camera original untouched, edit on a duplicate, and re-check the exported file in the viewer before you post. When you must edit, prefer software that preserves XMP on export — and verify the result instead of assuming it survived.
Does Facebook Support 360 Photos in 2026?
Yes, with conditions. Facebook still renders interactive 360 photos, but the upload has to satisfy all three requirements at the same time: an equirectangular projection, a 2:1 shape within the 6000 × 3000 ceiling, and GPano XMP metadata declaring ProjectionType = equirectangular. Satisfy all three and the photo becomes a sphere you can drag around. Miss one and you get a flat, stretched image with no explanation of why.
So when Facebook is not recognizing your 360 photo, work through the causes in that order: shape first, metadata second, platform last. Open the file in the 360° Panorama Viewer, read the two lines in the image check, and you will know within seconds which of the three you are actually dealing with.
