Publish 360 Photos to Google Street View in 2026: What Actually Works

Quick answer: The old route is gone: Google retired the Street View app in 2023, and no Google app will take a stitched panorama from your computer to published. What works in 2026 is this: stitch a clean 2:1 equirectangular JPG in Hugin, make sure it carries complete GPano photo-sphere metadata, then publish through a third-party tool that talks to Google’s Street View Publish API — a tour platform such as CloudPano or a desktop program such as Pano2VR — or add single 360 photos to Google Maps as photo contributions.

What actually changed

For years the workflow was simple: shoot with the Street View app or upload to it, and Google handled the rest. Google shut that app down in 2023 and moved on. The Street View Publish API still exists — it is the official channel third-party software uses to place photo spheres on Google Maps — but Google no longer offers a friendly consumer uploader for individual stitched panoramas. That is why every current “publish to Street View” button you see lives inside someone else’s software. Anyone telling you to “just use the Street View app” is working from an outdated tutorial.

The non-negotiables: format and GPano metadata

Google is strict about the file itself. Your panorama must be a JPEG in equirectangular projection with a 2:1 aspect ratio covering the full 360×180 sphere, and it must carry GPano XMP metadata — the photo-sphere block that tells Google this is a sphere rather than a very wide photo. The key GPano fields declare the projection type (equirectangular), the full sphere dimensions versus the cropped image dimensions, and the heading the centre of the image faces, which Google Maps needs to orient the sphere. Google publishes the exact requirements in its photo requirements for Street View and documents every GPano field in the Photo Sphere XMP metadata specification. If a sphere uploads as a flat, stretched image, missing or incomplete GPano data is almost always why.

Hugin exports the pixels; it does not guarantee a complete, publish-ready GPano block. Treat metadata as a separate finishing step: open the exported JPG in a metadata editor — ExifTool is the tool most photographers use for this — and check that the GPano fields are present and consistent (the cropped size must match the image size for a full sphere, and the full-sphere size must be exactly double width over height). Two minutes here saves a rejected upload later.

Route 1: Publish through a tour platform

Note: some links on this page are affiliate links. If you buy through them, we may earn a commission at no extra cost to you — it helps keep these guides free.

If you publish tours rather than single spheres, a platform is the path of least resistance. CloudPano, for example, connects your hosted tour to Google: the spheres go up through the Publish API with their locations, and the hotspots you built between rooms become the connections Google shows. Pricing checked on its site in October 2026: Pro is $22.50/month billed annually and Pro Plus is $33/month billed annually. This route makes the most sense for businesses — a restaurant, gym or estate agent — that want the tour on their own site and on Google from one upload.

Route 2: Publish from a desktop tool

Pano2VR, a desktop panorama converter, has Street View uploading built in: you load finished equirectangular images, set locations and north, and publish directly, without a hosting subscription. For photographers who already use it to build tours, it is the most direct surviving workflow — and it handles the GPano and location data as part of the process.

Route 3: Single photos via Google Maps contributions

For a one-off sphere — a viewpoint, a trailhead, a business frontage — you can simply add the photo to that place in Google Maps as a regular photo contribution. If the GPano metadata is complete, Maps recognises it as a photo sphere and displays it in the 360 viewer. What you give up versus the API routes is control: no connections to neighbouring spheres, no tour structure, and placement depends on the place listing existing. For a single image, though, it costs nothing and takes a minute.

Getting the sphere ready in Hugin

Everything upstream of publishing is the stitch itself: shoot for a full sphere, stitch equirectangular following our 360° panorama guide, patch the tripod spot, level the horizon, and set the initial view direction so the centre of the image faces the most important part of the scene — that centre becomes the heading Google orients by. Export the largest clean JPG your frames support; Google will compress it further, so start with quality to spare.

After publishing: check how it landed

Publishing is not the finish line. Once Google has processed a sphere — which can take anything from hours to a few days — open it on Maps and actually look around. Three checks catch most disappointments. First, the heading: the centre of your equirectangular image is the direction viewers face first, so if the sphere opens staring at a blank wall, re-set the heading (it lives in the GPano metadata as PoseHeadingDegrees) and republish. Second, the connections: on API-published tours, walk the arrows between spheres and confirm they jump in the direction a person would walk. Third, blurring: Google automatically blurs faces and licence plates, but check anything it may have missed — house numbers, documents, screens — because you are responsible for what you published.

Why your file quality still matters after Google compresses it

Google re-compresses every sphere it hosts, sometimes hard, and creators often ask why they should bother stitching at high quality for a platform that will shrink it anyway. The answer is that compression is not democratic: a clean, high-resolution, artefact-free master survives it far better than a small, noisy one. Seams, banding in skies and stitching ghosts get more visible after recompression, not less, and the fine detail that survives is exactly what separates a professional listing from a phone snapshot. Upload the best file Google’s requirements allow, and let the compression start from quality rather than from compromise.

FAQ

Can I still publish with the Google Street View app?

No. Google retired the Street View app in 2023. Publishing now happens through third-party software using the Street View Publish API, or by adding a metadata-complete 360 photo to Google Maps as a contribution.

Why does my uploaded panorama show as a flat, stretched photo?

Almost always because the GPano photo-sphere metadata is missing or incomplete, or the image is not a true 2:1 full sphere. Check the GPano block in a metadata editor and re-export a full 360×180 equirectangular JPG.

Does Hugin add GPano metadata automatically?

Not reliably enough to trust blindly. Hugin exports the equirectangular image; verify the GPano fields (projection type, full-sphere and cropped dimensions, heading) in a metadata editor before publishing.

Can I publish a connected tour, not just one photo?

Yes — tools using the Street View Publish API, such as CloudPano or Pano2VR, can publish multiple located spheres with connections between them. A plain Maps photo contribution cannot create connections.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *