Interior Design Studio · Spatial Lane · Capture Playbook

Polycam Capture Playbook — the whole-property sprint

Polycam's value is capture-time only. Every scan exported as GLB / OBJ / PLY / DXF / CSV is yours forever, and the studio's viewers are local three.js — no subscription needed after capture day. So before the Business trial ends, capture everything you might ever want a digital twin of. Worked example: a two-storey family home with a large front and back garden.

Trial ends ~6 Aug 2026 · Capture window: 4 days · Then cancel
01

Whole house in one scan, or room by room?

The most important question, answered first — because it determines the entire walk order.

Verdict — do both, they are different products

You cannot cleanly split a whole-house scan into rooms later. Polycam gives you a crop box, not a room-splitter — walls are shared surfaces, doorways smear between spaces, and long continuous walks accumulate drift (5–15 cm over a full floor loop is normal). Cutting a per-room twin out of a house mesh is painful and the result is worse than a dedicated capture.

The reverse is also true: separate room meshes cannot be reliably stitched into one house model afterwards — there is no shared coordinate frame to align them.

So each output gets its own dedicated pass. Three passes, three products — none substitutes for another.

PassModeDoorsWhat it producesWhy it can't be derived from the others
A · Per-room meshLiDARCLOSEDMeasurement-grade 3D twin of each room — the restyle asset, the viewer assetWhole-house walks drift; cropping rooms out is messy
B · Whole-floor walkLiDAROPENOne connected model per floor — the "explorer" view, hallway relationships, flowSeparate room meshes can't be stitched together
C · Floor plansROOMOPENParametric plan per room (walls / doors / windows), then merged into a whole-floor plan in-appMesh passes give geometry, not clean architectural plans
Room mode merge is the exception to the no-stitching rule. Polycam's Room mode (Apple RoomPlan) is built to combine per-room captures into one merged floor plan — do the merge in-app while you still have Business, and export the merged plan per floor. A merged whole-house floor plan is the single hardest thing to reconstruct after the trial ends.
02

Every mode, with settings

Five capture modes, each with a job. Settings below are the recommended starting points for this property — adjust only if the live preview looks wrong.

LiDAR mode

Rooms · stairs · patios · anything within ~5 m

Real-time depth mesh from the iPhone Pro sensor. Fast, reliable on blank walls where photogrammetry fails, accurate to roughly 1–2 cm. The workhorse for passes A and B.

Depth range3.0 m indoors · 5.0 m halls/outdoors
ProcessingSpace preset · finest voxel offered
PaceSlow — watch the live mesh paint in
AvoidMirrors, glass, direct sun stripes

Photo mode (photogrammetry)

Gardens · exterior · furniture · fine detail

Shoots overlapping photos, cloud-processes into a high-detail mesh. Far better than LiDAR beyond 5 m and for texture quality. Needs even light and stillness — wind-blown planting wrecks it.

CaptureAuto-shutter · ~70–80% overlap
Photo countObject 60–100 · garden 150–250
Processing detailFull (Raw for hero pieces)
Object maskingON for furniture · OFF for scenes

Room mode (floor plans)

Every room — the floor-plan lane

Apple RoomPlan: recognises walls, doors, windows and fixtures as parametric objects rather than raw mesh. One capture per room, then merge rooms into a whole-floor plan in-app.

Per captureOne room, door open, slow pan of every wall
MergeIn-app, per floor — before trial ends
ExportsCSV · DXF · PDF · PNG · SVG

Gaussian splats

1–2 hero rooms — photoreal walkthrough

Processed from a photo-mode-style capture into a radiance field: photoreal view synthesis meshes can't touch — reflections, soft materials, depth of field. The showpiece format for the studio's capability pack.

RoomsLiving room + kitchen (best light)
CaptureSlow orbits at 3 heights, lots of overlap
ExportPLY / SPLAT — before trial ends

360 mode

One pano per room — the photographic record

Ten seconds per room from the centre point. Not geometry — but a dated, complete visual record of every surface, and the fastest insurance-grade evidence you can capture. Do it in the same visit as the mesh pass.

03

Room technique — the walk

Same drill for every room, so the whole set comes out consistent. Budget 6–8 minutes per room across all three captures.

Before you press record

The sweep pattern (LiDAR mesh pass)

Stairs and the whole-floor walk

04

The four-day plan

Two floors, two gardens, one deadline. Export the same evening as each capture day — never let the cloud hold the only copy overnight if you can help it.

Day 1Ground floor

Every ground-floor room, three captures each

Per room: Room mode (door open) → LiDAR mesh (door closed) → 360 pano from the centre. Include the hall, under-stairs, utility, WC — the unglamorous spaces are the ones you'll want for storage and extension planning.

Finish with the whole-ground-floor LiDAR walk (all doors open), then merge the Room-mode captures into the ground-floor plan in-app. Evening: export everything, file it.

Day 2First floor

Upstairs, same drill, plus the stair link

All bedrooms, bathroom, landing, hot press, attic hatch if accessible. Same three captures per room. Then: the stairs capture (bottom hall to top landing), the whole-first-floor walk, and the first-floor plan merge. If Polycam will merge both floors into one building plan, do that too. Evening: export, file.

Day 3Outdoors + heroes

Gardens, exterior, splats, furniture

Morning (still air, soft light): back garden photo-mode capture, then front garden. LiDAR pass on hard landscaping — patio, steps, walls. Exterior orbit of the house. Afternoon indoors: Gaussian splat captures of the two hero rooms, photo-mode object captures of 3–5 hero furniture pieces. Evening: export, file.

Day 4Audit + cancel prep

Verify, re-shoot gaps, pull everything down

Walk the export checklist against the filing tree — every capture, every format. Tape-verify one wall per floor and one garden edge. Re-scan anything with holes. Confirm the merged floor plans exported. Then section 10.

05

Gardens — yes, with the right mode

Big front garden, big back garden: these are photo-mode jobs with a LiDAR assist, and the conditions matter more than the technique.

Conditions (non-negotiable)

The capture pattern (per garden)

LiDAR assist for the hard landscaping

Separate short LiDAR captures (5 m depth range) of the patio, steps, boundary walls, side passage, shed — anywhere you might later want real measurements for a landscaping design. LiDAR gives you the accurate ground geometry; photo mode gives you the look.

Set expectations: hedges and planting come out fuzzy — that's physics, not error. Ground planes, levels, paths, walls and structures come out genuinely usable, and that's what a garden redesign lane needs: the measured hard bones, with planting as replaceable dressing.
06

Exterior orbit & the cool extras

The captures that turn this from a scanning chore into a capability library.

House exterior (photo mode)

Furniture object library (photo mode, masking on)

Pick 3–5 hero pieces — the ones that would appear in any future restyle render. Orbit each at three heights, 60–100 photos, masking ON. Result: real 3D props to drop into future room designs instead of image-gen approximations.

The AR party trick (free forever)

Export every room mesh as USDZ as well as GLB. USDZ files open natively on iPhone in AR — point the phone at the floor and walk around a 1:1 or miniature copy of your own rooms. Zero subscription, zero viewer needed; it's built into iOS.

The 3D-print miniature

Export the whole-floor walks (or the exterior capture) as STL. Any print bureau — or a friend with a printer — can produce a physical miniature of the house. Gimmick? Partly. But it's also the single most persuasive demo of the spatial lane that exists: here is a physical object made from a phone walk-around.

In-app measurements while you still can

Polycam lets you drop measurements on any capture in-app. On day 4, take screenshots of key measurements (room widths, ceiling heights, garden lengths) as a belt-and-braces record alongside the CSV exports.

07

Export discipline

The subscription's real product is the export set. Same-evening exports, every format, filed to the same tree as the existing properties. Assume the cloud copy dies when the trial does.

Capture typeExport formatsWhy each
Room mesh (LiDAR)GLB + OBJ + USDZGLB = our three.js viewers · OBJ = universal interop · USDZ = iPhone AR
Room mesh (LiDAR)PLYPoint cloud — the raw measurement record
Floor plan (Room mode)CSV + DXF + PDF + PNG + SVGCSV = dimensions data · DXF = CAD · PDF/PNG/SVG = human-readable
Merged floor planSame five, per floorThe un-reconstructable asset — do not skip
Garden / exterior (photo)GLB + OBJ + PLYViewer + interop + raw cloud
Hero rooms (splat)PLY / SPLATRadiance field — locked behind sub after cancel
Whole-floor walksGLB + STLExplorer model + 3D-print miniature
Every room360 pano imageInsurance-grade dated visual record

Filing tree

departments/interior-restyle/projects/family-home/ └─ scan/2026-08-0X/ ├─ DIMENSIONS.md ← single source of truth · UNVERIFIED until taped ├─ ground-floor/ │ ├─ living-room/ ← floorplan/ + mesh/ + pointcloud/ + 360/ │ ├─ kitchen/ │ ├─ hall-understairs/ │ ├─ _floor-walk/ ← the continuous pass (GLB + STL) │ └─ _floor-plan-merged/ ← CSV + DXF + PDF + PNG + SVG ├─ first-floor/ ← same pattern + stairs/ ├─ outdoors/ │ ├─ front-garden/ ├─ back-garden/ ├─ hard-landscaping/ └─ exterior-orbit/ └─ heroes/ ├─ splat-living-room/ ├─ splat-kitchen/ └─ objects/<piece>/
Naming: keep Polycam's capture names boring and descriptive at capture time (ground-living-mesh, ff-bed2-plan) — attribution by filename beats memory three days later.
08

Tape verification

One tape measurement per zone turns "scan values" into "verified dimensions" — the same protocol that upgraded the games room from UNVERIFIED to VERIFIED.

09

What we build after — the payoff list

Everything below runs on the exported files and local tooling. None of it needs Polycam again.

BuildWhat it isRuns on
Per-room 3D viewersDrag-to-spin twins of every room, same as the head office pairGLB + three.js (local)
House explorerFloor-explorer pattern: pick a floor, pick a room, spin it — the whole home as one navigable dashboard propertyGLB + floor-walk models
Restyle lane, any room, foreverAny room can enter the guide + gate restyle pipeline at any future date — the twin already existsMesh + survey photos
Garden design laneLandscaping restyles on measured hard bones — patios, planting schemes, garden roomsGarden meshes + LiDAR assists
Insurance archiveDated 360 + mesh record of every room and its contents — best-possible claims evidence360 panos + meshes, filed
Measured-survey substituteTape-verified plans ≈ the €500–1,500 survey an architect orders before extension workMerged DXF/CSV plans
Furniture prop libraryReal pieces as 3D props in future designsObject GLBs
AR walkthroughsRooms at 1:1 or dollhouse scale on any iPhone, nativelyUSDZ
Printed miniaturePhysical model of the house — the spatial lane's best demo objectSTL
Dissection calibrationPhoto-to-massing pipeline scored against real measured geometry of the same buildingExterior orbit mesh
10

Cancel-day checklist

Only after every line passes.

Privacy standing rule. Family-home captures are family content: scan exports and floor-plan CSVs can carry address and GPS metadata. They live in the repo and the local dashboard only — never deployed, never shared. This playbook page stays generic (no address, no photos, no captures) — that is why it, alone, is allowed on Cloudflare.