> ## Content Index
> Fetch the complete content index at: https://gothru.co/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# 360 Editing Software: Prepare and Check 360 Photos
- URL: https://gothru.co/blog/360-editing-software/
- Published: 2026-11-17T19:24:41.000Z
- Updated: 2026-11-17T19:24:41.000Z
- Description: A practical guide to choosing software for an existing 360 still, repairing its visible defects, and checking the saved panorama before a tour or Photo Sphere upload.
- Author: Alin Bugeag
- Tags: 360 Photography

A stitched 360 photo needs more than a pleasing edit in a flat image window. Choose software that can show the image as a sphere, make the needed repair, and leave you with a file your destination can actually use. The last check belongs on the exported copy, since a resize, crop or save operation can change pixels or metadata after the working file looked right.

This guide follows an already captured still panorama through diagnosis, repair and export. If you have unstitched camera frames, a cubemap set or video, identify that first. Each starts at a different point in the workflow. You can prepare a panorama in a desktop editor, but scene connections and acceptance by a hosting or mapping platform are separate jobs.

## What kind of 360 file do you have?

Start by opening a copy of the file and checking its dimensions, extension and appearance. A full spherical equirectangular still is usually a wide rectangle containing the complete view around the camera and from floor to ceiling. Its flat preview looks stretched at the top and bottom. In a spherical viewer, you can turn through the scene and look up and down. [PTGui's projection guide](https://www.ptgui.com/man/projections.html) explains why equirectangular output is used for a full 360° by 180° sphere.

These inputs call for different software jobs:

- An already stitched equirectangular JPG or PNG needs visual inspection and possibly retouching, leveling, metadata work or export. That is the main route here.
- Separate fisheye shots or bracketed source frames still need stitching or blending. A color adjustment to one frame does not give you a completed sphere. GoThru's [older free-stitching walkthrough](https://gothru.co/blog/how-to-stitch-360-images-for-free/) discusses a Gigapano/Autopano route, but check the software's current availability and fit before following older installation instructions.
- A set of six cubemap faces represents different views of a sphere. Preserve each face's dimensions and orientation if you plan to reconstruct an equirectangular file. GoThru's [equirectangular-to-cubemap guide](https://gothru.co/360-photo-studio/docs/convert-between-equirectangular-and-cubemap-images/) covers that conversion and the return trip.
- A 360 video calls for a video editor or extraction workflow. Google [Street View Studio's upload instructions](https://support.google.com/maps/answer/7546470?hl=en) describe an outdoor-video route that accepts `.mp4` and `.mov`, not the still-photo preparation in this article.

A camera companion app may be the first stop if the camera produces a native project or an unexported capture. Export a stitched still using that camera's current instructions, then inspect the resulting file. Do not assume a general panorama editor can open a proprietary camera project or develop its RAW source files. Similarly, panorama editing software aimed at joining landscape frames solves an earlier problem than repairing a finished spherical image.

A quick sanity check can save a long edit. If the file is a conventional wide landscape photo, its large width alone does not make it a full sphere. Turn it in a viewer and look for complete coverage at the top and bottom. If the viewer opens a flat image, investigate the projection and metadata before trying to publish it as 360 content.

## Choose software for the edit you actually need

Choose by the output and the defects, not by the number of tools in a feature list. A 360 camera editor can be ideal for exporting its own native footage, while a still-photo editor is more useful after stitching. For an existing panorama, evaluate a candidate with one disposable copy of your own file and verify the saved result.

- For visual review, require a spherical preview with a useful zoom level and access to the seam, zenith and nadir. A flat thumbnail will miss distortions that become obvious when you turn your head in a viewer.
- For a crooked horizon, look for spherical-aware leveling or a method that keeps the full projection intact. Inspect vertical walls at several headings after the change.
- For exposure and color, check whether the tool can balance the scene without creating a bright/dark boundary at the wrap. If you captured bracketed panoramas, the [GoThru Enfuse instructions](https://gothru.co/360-photo-studio/docs/create-hdr-360-images-with-enfuse/) describe blending aligned exposures from the same scene. Blending cannot recreate missing capture detail or fix a bad stitch.
- For a visible tripod, look for a nadir patch or a retouching route that lets you inspect the result from inside the sphere. A logo may be acceptable in a private tour but can be distracting at other destinations.
- For a resize or delivery copy, check that the software reports actual output dimensions, file type and metadata. A smaller byte count by itself says little about projection or sharpness.

[GoThru Photo Studio](https://gothru.co/gothru-photo-studio.html) is one desktop option for the existing-still route. Its [getting-started documentation](https://gothru.co/360-photo-studio/docs/getting-started-with-gothru-photo-studio/) describes an image workspace and standard equirectangular JPG and PNG input on Windows and macOS. The [interactive preview guide](https://gothru.co/360-photo-studio/docs/preview-and-review-360-images/) describes the inspection job. That documentation does not establish that every native camera file, RAW source, export destination or plan feature works for your project.

![The same interior panorama shown in GoThru Photo Studio's spherical Preview, aimed down toward the entry and floor.](https://gothru.co/blog/content/images/2026/11/p3-photo-studio-spherical-preview-owner-crop-1374x780.webp)

*GoThru Photo Studio Preview shows an alternate spherical view of the panorama pictured in the article hero. This is a view of the loaded image, not a verified edited export.*

Try the exact operation you need on a copied file. Record its starting dimensions, projection tag if present, and how it looks in a separate viewer. Export, reopen that saved copy, and compare. If the app can display an image but cannot save it in the form your recipient requests, choose another export route rather than inferring compatibility from the preview.

## Preserve the sphere while editing

A full equirectangular panorama maps longitude across the width and latitude down the height. Its left and right edges meet in the viewer. The top converges at the zenith, and the bottom converges at the nadir. A full 360° by 180° image is commonly 2:1 in pixel dimensions, as [PTGui describes](https://www.ptgui.com/man/projections.html). This geometry explains why a normal rectangular crop can remove part of the view even when the flat result looks neatly framed.

![Owner-supplied equirectangular interior panorama annotated with relative longitude and latitude, joined wrap edges, zenith and nadir.](https://gothru.co/blog/content/images/2026/11/p3-equirectangular-real-panorama-candidate-960x900.png)

Keep an untouched master and edit a working copy. If an adjustment changes the canvas, find out whether it rotated the sphere, changed the projection or merely cut pixels away. A flat crop can turn a full-sphere file into a partial panorama. It can also leave the original full-sphere metadata attached to a new rectangle, making a viewer place the surviving pixels incorrectly. The 2:1 shortcut applies to a full sphere, not every legitimately partial panoramic image.

The wrap seam needs special care. Imagine a doorway straddling the far left and right sides of the flat file. A local exposure adjustment on only one edge may become a conspicuous vertical line when those edges meet. Inspect the join after any tonal change, clone work or overlay. Near the poles, a circular patch or straight brush stroke in flat coordinates can look surprisingly large or warped from inside the sphere. A tool that presents a rectilinear view or cube face for retouching can make local work easier, provided you return to the equirectangular export and inspect the reconstructed seams. The [GoThru cubemap conversion instructions](https://gothru.co/360-photo-studio/docs/convert-between-equirectangular-and-cubemap-images/) explicitly call for reviewing the output after reassembly.

Treat stitching and retouching as separate diagnoses. If the same chair leg appears twice because the source viewpoints disagreed, blending color over the split may hide it in a flat strip but rarely fixes its geometry from every angle. Return to the stitch or source capture when overlap and parallax are the cause. If the structure is sound but a small tripod base remains, a local nadir repair may be enough.

Changes to compass orientation also deserve a check. The direction a photo first faces is distinct from leveling it. Rotate or recenter a panorama only when you understand how the destination interprets heading, then verify the view after export. Google's [GPano specification](https://developers.google.com/streetview/spherical-metadata) lists separate heading, pitch and roll fields. A corrected-looking preview does not prove those stored fields still describe the saved image.

## Inspect horizon, seams, exposure and nadir in the viewer

Inspect the panorama interactively before choosing a repair. Start at eye level and turn through a full circle slowly. Look up, then down. Zoom toward transitions between source views and toward anything a visitor will study, such as text, windows or furniture edges. GoThru's [preview checklist](https://gothru.co/360-photo-studio/docs/preview-and-review-360-images/) covers horizon, seams, nadir, zenith, exposure and privacy in the interactive view.

A repeatable pass catches specific faults:

1. Follow the horizon through a complete turn. A tilted room may need spherical leveling. If a single wall bends while the rest looks level, investigate stitching or lens geometry instead of rotating the entire sphere.
2. Cross the left/right wrap and every suspected source join. Look for duplicated edges, abruptly changing color, missing pixels and moving subjects. A tiny seam on the flat image can be prominent when the viewer puts it in front of you.
3. Look at bright windows and dark corners at a reasonable zoom. If highlight detail is absent in all captures, brightening a finished JPEG cannot recover it. When matched bracketed panoramas exist, blending may provide a better source for the edit.
4. Tilt the view down. Check the tripod, photographer shadow and any patch boundary. GoThru documents a desktop [logo-nadir workflow](https://gothru.co/360-photo-studio/docs/logo-nadir-patching/) and a separate [tour-dashboard Nadir Manager](https://gothru.co/docs/how-to-apply-a-nadir-image-to-your-panoramas-using-gothru/). The latter is a tour operation, not a step required to edit the local file.
5. Tilt up and inspect the zenith for holes, blur and mismatched ceiling detail. Then inspect people, faces, plates, screens, documents and reflections for privacy issues. A defect can be visible in the source without having been resolved for a hosted tour or map submission.

Check the intended destination's own quality rules as well. Google's [Photo Sphere guidance](https://support.google.com/maps/answer/7012050?hl=en) calls out horizon gaps, significant stitching errors, insufficient light or dark detail, blur and distracting nadir effects. Those are Google's destination checks, not a promise that an editor can repair each fault automatically. If a detail is irretrievable, keep the limitation visible in the review decision and consider a different source or recapture.

After each substantial repair, review the entire sphere rather than only the retouched area. A local patch can have a soft edge at one angle and a clear shape at another. If you must demonstrate a before/after result to a client, use the same source, viewing angle and zoom, and label the actual operation performed. A generic pair of attractive panoramas says little about whether the output survived export.

![GoThru Photo Studio Auto Level queue showing one panorama queued with roll and pitch values and Save as New File selected.](https://gothru.co/blog/content/images/2026/11/p3-photo-studio-auto-level-queued-owner-redacted-1553x285.webp)

*Auto Level in GoThru Photo Studio 1.2.1, before applying the queued adjustment.*

![Full equirectangular views of the same interior panorama, labeled before and after Auto Level.](https://gothru.co/blog/content/images/2026/11/p3-auto-level-before-after-review-1200.webp)

*The same panorama before and after Auto Level in GoThru Photo Studio, shown as full flat equirectangular images. Compare the door frames and ceiling trim. The pair is a visual check, not a measurement of the adjustment.*

## Pick an export for the destination

Export for a named destination and keep the high-quality working copy. File extensions, aspect ratio, bytes and embedded metadata are separate properties. A JPEG can be small enough to send yet fail a destination's pixel minimum. A PNG may preserve pixels but be unsuitable for a recipient that specifically asks for JPEG. Ask the receiving system what it currently accepts before changing a good master to satisfy an assumed rule.

For a hosted tour, determine the accepted file type, resolution, size and orientation in the current tour workflow. Check those rules against your actual export. There is no universal GoThru import limit implied by Google's requirements below. Tour construction can also involve scene order, connections, navigation and hosting after the stills are prepared. Those are later tasks, not properties a file editor can guarantee.

For a still Photo Sphere on Google Maps, Google's [create and publish guidance](https://support.google.com/maps/answer/7012050?hl=en) currently lists a 2:1 aspect ratio, at least 3,840 × 1,920 pixels and no more than 75 MB, along with visual quality checks. Apply these figures only if that is the destination. A partial crop can be validly described in GPano metadata, but it is not automatically eligible under a destination rule asking for a full 2:1 Photo Sphere. Check Google's current rule and the actual upload route rather than stretching a partial image until its dimensions look compliant. Meeting the numeric limits or adding tags does not guarantee acceptance or display.

Resizing changes pixel dimensions. Compression changes encoding and may introduce visible artifacts without changing dimensions. GoThru documents [batch resizing](https://gothru.co/360-photo-studio/docs/batch-image-resize/) and [image minification](https://gothru.co/360-photo-studio/docs/image-minifier/) as distinct operations. Preserve the full-sphere ratio if you resize a full equirectangular image, then compare fine text and seam detail at the exported resolution. Upscaling a soft source adds pixels without restoring captured detail. An older [GoThru dashboard resize guide](https://gothru.co/docs/how-to-resize-360-images-with-gothru/) describes editing images inside a tour. Use it only for that dashboard job, and do not transfer its older upload assertions to the desktop editor or to Google's current rule.

If the input is video, leave this still-photo export path. Street View Studio's [video instructions](https://support.google.com/maps/answer/7546470?hl=en) describe 360 video with location data and processing on Google's side. A still JPEG prepared here is not a substitute for that `.mp4` or `.mov` route, and neither route promises connected blue-line coverage.

## Check metadata on the exported file

Read the saved file's pixels and tags after export. Do not rely on the source file's metadata panel. An editor may resize the image, change the canvas or remove embedded fields during a save. A viewer that recognizes the source can show the new copy as a flat photo or distort a partial crop if its stored geometry no longer matches the pixels.

Three kinds of information are easy to confuse. GPano is an XMP namespace describing how a panorama should be interpreted. Ordinary EXIF fields can carry capture or location data. The visible image is the actual pixel content. A GPS coordinate does not make a flat photo spherical, and a GPano projection tag cannot restore missing sky or floor. GoThru has separate documentation for [editing GPS coordinates](https://gothru.co/360-photo-studio/docs/how-to-update-gps-location-of-an-image/) and [setting an image as 360 with its EXIF-labelled tool](https://gothru.co/360-photo-studio/docs/how-to-set-an-image-as-a-360deg-image-using-exif-metadata/). The tool's name alone does not prove that every destination's required GPano XMP fields are present, so inspect the export itself.

Google's [Photo Sphere XMP specification](https://developers.google.com/streetview/spherical-metadata) names `GPano:ProjectionType` and the cropped-area and full-panorama dimensions and offsets. For a full equirectangular image, the crop normally covers the entire canvas. The cropped width and height should match the actual saved pixel dimensions, and the left and top offsets should describe where that crop sits in the full sphere. If you scale the image, update the related dimensions and offsets consistently. If you crop it, preserve the relationship between the surviving rectangle and the original full spherical canvas.

Google's own partial-sphere example uses a 4,000 × 2,000 full canvas with a 2,300 × 1,042 saved crop, located 90 pixels from the left and 128 pixels from the top. The crop is not 2:1, and those numbers are an illustration of the metadata model, not a GoThru test file or an approval threshold for Google Maps. A partial image needs its own truthful crop fields. Relabeling a cropped rectangle as a complete sphere misrepresents the missing view.

Use an image-properties reader or metadata inspection tool that shows the exported file's actual pixel width and height, file format, EXIF fields and GPano XMP separately. Write down the observed values rather than assuming they were copied. For a full sphere intended for Google, check the relevant projection and dimension fields and whether heading information required for Maps display is appropriate. Google's specification says `GPano:PoseHeadingDegrees` is required for display on Google Maps, even though it is otherwise optional in the namespace. Location and heading should describe the real scene rather than guessed coordinates.

Finally, reopen that same saved file in a spherical viewer. If the viewer displays it flat, compare its real dimensions and GPano fields with the export settings. If it shows an impossible sky, stretched walls or displaced crop, fix the pixels or metadata as appropriate and save another copy. Metadata read-back is an automated check, while the visual inspection still needs a person.

## Run a preflight on the saved panorama

A preflight should be short enough to repeat for each delivery batch and precise enough to catch a wrong file. Give the exported copy a distinct name, keep its master separate and record the destination beside it. Run the checks on the copy you will actually transfer, not on a previously approved working version.

- Confirm you can use and distribute the image. Review faces, plates, screens, private documents, location details and reflections. Decide which visible material must be removed or blurred before the destination's own privacy review.
- Record the exact saved filename, file type, byte size and pixel width and height. Compare each against the destination's current instructions. If a format is rejected, return to the export setting instead of renaming the extension.
- For a full sphere, check the full equirectangular geometry. For a partial panorama, record its intended field of view and crop metadata. Do not force every partial image to 2:1 by stretching it.
- Inspect the GPano XMP projection and dimensions when the recipient uses them. Check EXIF location separately if location is needed. Compare the saved file's pixel measurements with its embedded cropped-area dimensions.
- Open the saved copy in a spherical viewer and turn through the seam. Look up, down and into high-contrast details. Revisit any retouched region at a useful zoom.
- Try the file in the intended recipient's current workflow. Confirm what the receiving app imported, then inspect the displayed result. An accepted upload or processing message is an intermediate state, not proof that visitors can see the final image or navigate between scenes.

A one-line handoff record can make batch review practical. For example, use blank fields for `filename`, `destination`, `saved width × height`, `format and bytes`, `GPano projection and crop`, `EXIF location if required`, `viewer pass`, `privacy pass` and `destination result`. Fill those fields from your own file and observed result. There is no sample pass score here, because this article has not run a benchmark on owner-approved images.

Do the checks in that order when possible. A privacy or rights failure should stop distribution before you spend time testing an upload. If the panorama fails a visual check, keep the output as a working copy and revisit the source edit. If it passes the file checks but the recipient rejects it, capture the recipient's current error and compare its stated input rules before changing anything else.

## Where does a prepared panorama go next?

A prepared still can be handed to a tour workflow, shared as a standalone sphere or submitted through an eligible still-photo path. Choose the destination before treating the export as finished. The same image can require different packaging for a hosted tour and for Google Maps, and a technically correct panorama can still need connections, privacy review or platform processing.

In a GoThru tour, uploading prepared scenes is followed by tour construction in GoThru Moderator. The [GoThru guide to a connected no-listing tour](https://gothru.co/docs/how-to-upload-360-images-to-google-without-a-business-listing/) shows one particular project route. Check current access and instructions for your own project. Fix a seam or visible face in the file before upload. Connection choices and blur/privacy review remain separate responsibilities once images are in the tour. Google describes [third-party apps for linking Photo Spheres](https://support.google.com/maps/answer/7012050?hl=en), but neither a completed edit nor a connected tour guarantees a Maps result.

For an individual Google Maps Photo Sphere, use Google's current [still-photo publication guidance](https://support.google.com/maps/answer/7012050?hl=en) and inspect what appears after submission and processing. Do not confuse this with Street View Studio's outdoor 360-video workflow. If your project started as outdoor video and uses GoThru Street Builder to extract panoramas, that handoff still needs connection and review before submission, followed by an independent check on Maps. It is a different path from repairing one existing still.

If your main job is preparing and checking existing equirectangular stills on a computer, compare your file and operating system with [GoThru Photo Studio's getting-started guidance](https://gothru.co/360-photo-studio/docs/getting-started-with-gothru-photo-studio/) and use the [GoThru Photo Studio download chooser](https://gothru.co/download/gothru-photo-studio) if it fits. Keep the untouched master and saved-file preflight record whichever editor you choose.