Asset management for hunts
Prepare the images and 3D files your hunt and objects need before you build or launch.
Gather the images and 3D model files your hunt needs and have them ready before you build, so setup runs smoothly and you avoid rework later. A 3D model file is a rotatable digital object your design team provides.
Assets you'll need
A hunt combines a banner and a map up front, then 3D objects with an optional skybox file.
Banner Image
OptionalThe header image for an activity, offer, receipt challenge, or treasure hunt.
- Optional
- Size900 × 600 px
- Aspect ratio3:2
- FormatsJPEG / WEBP / PNG
Map Image
OptionalA custom map players read to find hunt objects — it acts as a background layer, with the objects dropped on top.
- Optional
- Aspect ratioFree — vertical recommended
- FormatsJPEG / PNG / SVG / WEBP
Keep it clean and uncluttered so the objects read clearly. Any aspect ratio works, but a vertical (portrait) map fills phone screens best.
3D Model
RequiredThe 3D object for a catcher, 3D selection, or treasure hunt — chosen from your 3D library.
- Required
- FormatsGLB · USDZ
GLB powers 3D and Android AR; add USDZ for the best experience on iPhone and iPad. Keep models low-poly and under ~5 MB so they load fast on phones.
Skybox Image
OptionalThe 360° surround that wraps the scene in a 3D hunt object.
- Optional
- Aspect ratio2:1
- FormatsJPEG / PNG / HDR
Use a 3D badge as a hunt object
Hunt objects can be any 3D model — including a 3D badge. See the available shapes and how to set up front/back artwork in Design a 3D badge.
For every image spec in one place, see Image & asset specs.
The core asset checklist
Most hunts only need a small, predictable set of files:
| Asset | Where it is used | When it is required |
|---|---|---|
| Hunt banner image | Hunt General tab | Required for the hunt entry point |
| Object 3D model file | Each object | Required for 3D First and AR First objects |
| USDZ version of the object | AR object on iPhone and iPad | Recommended whenever the hunt should work well on Apple devices |
| Treasure hunt map | Hunt Treasure Hunt Configuration | Optional, only when the hunt uses a map |
| Completion question image | Hunt Treasure Hunt Configuration | Optional, only when the final hunt question needs visual support |
| Optional background scene image | Object advanced 3D settings | Optional, only when the object uses a surrounding background |
Prepare assets before you build
The cleanest workflow is to prepare the hunt's files before you begin detailed configuration:
- choose the final hunt banner
- prepare one approved 3D model per object
- keep the GLB and USDZ versions aligned to the same design
- decide which objects need map markers, hints, or a background scene
This reduces rework later when you start testing the route on real devices.
Match the files to the experience mode
If you just want the simplest path, prepare one 3D model file per object and use 3D First first.
| Experience mode | What to prepare |
|---|---|
| 3D First | The object's 3D model file |
| AR First | The object's GLB file, plus USDZ when you want a better experience on iPhone and iPad |
If you are unsure which mode to use yet, start by checking the model in 3D First, then switch to AR First once the model, interaction, and route all work as expected.
Hunt-level assets versus object-level assets
It helps to treat the hunt and object files differently:
- the hunt banner, map, and optional completion-question image support the overall route
- each object's 3D model file supports one discovery moment inside that route
For example, the hunt banner might introduce a "Space Explorer Trail," while each object's model represents a different planet-themed collectible participants discover along the way.
Check the assets before launch
Before you publish:
- open every object once in preview
- test AR objects on the devices that matter most
- confirm the hunt banner looks right on the hunt entry point
- confirm map markers and physical placement still match
Use validation as the final asset check
Publish validation is good at catching missing banners, missing object model files, and incomplete AR file sets. Treat it as the last checkpoint, not the first one.
If something's blocked
A few common reasons and how to fix them:
- The hunt has no banner image — the entry point has nothing to show participants. Upload the banner in the General tab before publishing.
- An object has no 3D model file — participants will have nothing to view when they open the object. Add the model file to the object before testing or launching.
- An AR object is missing its GLB file — the GLB is required for augmented reality to work. Upload the GLB version of the object's 3D model.
- An AR object is missing its USDZ file — the USDZ gives a good experience on iPhone and iPad. Upload the USDZ version when you want to support Apple devices well.
Related
Configure hunt objects — 3D mode
Attach the asset and finish a 3D-first object.
Configure hunt objects — AR mode
Prepare the mobile file set needed for an AR-first experience.
Test the hunt
Run device checks before you rely on the asset set in a live venue.
3D/AR rendering issues
Diagnose problems caused by missing files, unsupported devices, or asset setup issues.