Basic

Import one panorama

Your image must be complete and 2:1. Use a JPEG, PNG, or HEIC that is at least 4,096 × 2,048 pixels. A recommended size is 12,288 × 6,144.
  1. Open Places, then choose Import.
  2. Choose Import a View. Pick Photos, Files, or URL.
  3. Select the panorama. For URL, paste a direct public HTTPS image link rather than a webpage.
  4. Wait while Locus prepares it. Locus creates the images it needs for preview and Room lighting on your device.
  5. Open it in Places. Pair the new View with any Room, then choose Enter Place.

If the panorama is already online, the faster route is Apply a panorama from Locus Browser. You can try it without using an import first.

Better results

Prepare the image before importing

A flat two-to-one equirectangular panorama of an autumn hillside
A View image looks unusually wide because it stores the full 360° sphere in one flat 2:1 image.

In Locus

Fine-tune the View

In Places, open the menu for your View and choose Edit View. Adjust Turn the View first, then View Brightness, Contrast, Color, Room Lighting, and optional Sunlight. These settings are saved for this View.

Separate what you see from how the Room is lit. View Brightness changes the panorama. Room Lighting changes how strongly that View lights the 3D Room.

Advanced

Package a reusable View

For stable identity, in-place updates, media and masks, an optional sourceImage, View-owned USDZ midground scenery and water, sound, provenance, and optional bundled Experiences, use a complete Package v2 ZIP in Locus 1.2.1 or later:

my-view.zip
├── locusplace.json
└── catalog/
    └── destinations/<destination-id>/
        ├── destination.json
        ├── panorama.jpg
        ├── thumbnail.jpg
        └── provenance.json

Keep locusplace.json and catalog/ directly at the ZIP root. Import the ZIP from Files or a direct public HTTPS URL. Locus checks stable IDs, versions, file hashes and inventory, safe paths, resource limits, capabilities, and minimum app version.

Internal and external Views use one pure-data contract. If the installed Locus binary can render a supported Room or View field, a complete public package can declare it under the same validation and version rules. Packages cannot carry scripts, plugins, dynamic libraries, or executable extensions. See the complete View source and midground reference.

The current public packer and validator instead create a legacy/simple flat View ZIP. That compatibility format still supports a panorama, thumbnail, provenance, panorama.initialYawDegrees, appearance, Room-lighting image, optional sunlight, and sound, but every import receives a new UUID:

my-view.zip
├── view.json
├── provenance.json
├── panorama.jpg
├── thumbnail.jpg
└── lighting.jpg       # optional
  1. Create the panorama and thumbnail. Keep the panorama complete and exactly 2:1.
  2. Choose the delivery contract. Use complete Package v2 for feature-complete delivery and updates, or the flat layout for simple compatibility.
  3. Record provenance. State who made it, what rights apply, what changed, and whether AI was used.
  4. Validate the exact ZIP. The downloadable public tools validate only the flat compatibility format.