3D capture planning
A practical guide to realitycapture pricing
realitycapture pricing makes more sense when you separate software access from the real cost of a capture project. Use this guide to identify the variables before you commit time or equipment.
The value in one line
A useful pricing decision starts with scope: match your capture method, output needs, and operating setup before comparing any quoted figure.
Three cost levers to check
These three checks turn a vague price question into a project-specific decision.
-
1
Define the output
Decide whether you need a textured mesh, a measured model, a scene for visualization, or another deliverable. More demanding outputs can change capture, processing, and review requirements.
-
2
Separate access from operations
Consider the software access question independently from photography, scanning, storage, hardware, processing time, and specialist labor. The application is only one part of the budget.
-
3
Test the workflow first
Run a small representative set of images before planning a full production job. This exposes coverage, quality, and export issues while the cost of change is still low.
A step-by-step budget check
Use these checkpoints in order so a headline figure does not hide the work around it.
- Confirm the capture scope
- 01
- List the operating costs
- 02
- Validate the output workflow
- 03
- Compare the complete plan
- 04
Limits and edges
A software figure rarely describes the whole project. The useful comparison is between the visible access question and the wider production reality.
Headline price
Complete project view
- Software access
- Complete project budget
What it covers
Software access
The right to use the application under the applicable access terms
Complete project budget
All resources required to capture, process, review, and deliver the result
Capture equipment
Software access
Usually considered separately
Complete project budget
Camera, drone, scanner, targets, or supporting equipment may be relevant
Processing resources
Software access
May not describe workstation, storage, or processing requirements
Complete project budget
Includes the hardware, storage, and time needed for the workflow
People and skills
Software access
Does not replace planning, capture, cleanup, or quality control
Complete project budget
Accounts for operator time and specialist review where needed
Output requirements
Software access
Does not determine the mesh, texture, measurement, or export specification
Complete project budget
Budget is shaped by the deliverable and its acceptance criteria
Best use
Software access
Answering whether access is suitable for your situation
Complete project budget
Deciding whether the entire project is practical and affordable
Main risk
Software access
Treating access as the only cost
Complete project budget
Underestimating capture preparation, rework, or delivery effort
Frequently asked questions
The answer depends on the current access terms and your use case, so a single figure may not describe every situation. Check the applicable terms for your project, then budget separately for capture, hardware, processing, storage, and delivery.
Some users may qualify for a free or no-cost access route depending on their circumstances and the terms in effect. Review the dedicated reality capture free guidance and confirm the conditions that apply before planning production work.
Include image or scan capture, equipment, operator time, workstation resources, storage, quality checks, cleanup, and export or delivery work. These costs can matter even when software access is free or already available.
Define the output, estimate the capture scope, and run a small representative test. Then compare the complete workflow cost rather than comparing software access figures alone.