Separate setup, production, and ongoing costs
Setup includes equipment, supports, lighting tests, and storefront implementation. Production includes preparation, capture, editing, quality control, and reshoots for each product. Ongoing costs include the viewer subscription, hosted usage, and maintenance of your storefront integration.
Keep these categories separate when comparing in-house production with a photography provider. A viewer subscription is not a quote for photographs, retouching, hardware, or custom development. Use the current pricing page for plan amounts, billing options, included usage, and overage terms rather than copying a subscription schedule into your production estimate.
Hosted versus self-hosted viewer costs
With a hosted viewer such as SpinShot, budget the subscription, storage and delivery overage, and your storefront implementation. The provider runs the hosted image-delivery and viewer stack. You still supply the photographs and maintain your own storefront; hosting does not eliminate capture costs or every developer task.
Self-hosting can be appropriate if you need control of your viewer stack and can maintain it. Budget any viewer license, object storage, image processing, CDN traffic, HTTPS configuration, backups, monitoring, software updates, and developer time for browser and theme changes. Existing infrastructure can lower incremental cost, but it does not make ongoing maintenance free.
Compare both options using the same image library, traffic, zoom behavior, and service requirements. Self-hosting is not automatically cheaper or more expensive: usage and available engineering capacity decide. SpinShot is described here as a hosted service; this comparison is not a claim that a self-hosted SpinShot license is available.
API automation and Enterprise requirements
The published Business plan lists Full API Access, and Enterprise includes Business features. The REST API documentation describes creating projects and products, uploading images, finishing uploads, and embedding views. The viewer API separately documents interaction settings and query-parameter customization. An API can automate work, but building, securing, testing, and maintaining that integration still takes engineering time.
Do not infer that every API capability has the same entitlement on every plan. Confirm the endpoints, authentication requirements, usage limits, and any plan restrictions with sales before choosing a subscription. No separate per-call API price is quoted here because the inspected public documentation does not establish one.
Enterprise lists white-label options, dedicated support, custom analytics and integrations, onboarding, an SLA guarantee, and volume discounts, with custom pricing and overage terms. Ask sales for written scope, service levels, usage allowances, and a quote; these are not a promise of unlimited traffic, included custom development, or a particular SLA target.
Storage and bandwidth are different budget lines
Storage is the hosted image library; bandwidth is data delivered when visitors use the published views. A larger catalog can increase storage even with modest traffic. Popular product pages, larger images, zoom use, and denser sequences can increase delivery usage. Measure a representative pilot rather than equating a product count with a fixed plan allowance.
Record the exported image library size and actual delivery usage during a pilot. Compare those measurements with current plan allowances and overage terms on the pricing page; product count alone cannot predict either usage line.
Capture and retouching determine per-product work
Include cleaning, preparation, mounting, centering, lighting tests, frame capture, editing, quality control, and upload time. Count reshoots and the final check of the published spin. A reflective watch or a mounted ring may need more setup and fixture cleanup than a simple matte object.
Ask a photography provider to quote the frame count, resolution, background, retouching scope, still-image deliverables, usage rights, and number of products. No fixed per-product photography rate is published here. Compare quotes for the same deliverables rather than treating a single still image and a complete rotation as equivalent work.
Equipment and storefront implementation are separate
Budget for the camera and lens, tripod, lights and diffusion, background, rotating platform, and appropriate product supports. An existing studio or manual turntable can be enough for a pilot. Consider automation when consistent rotation and repeat throughput justify the investment; consult the hardware pages for current equipment details and purchasing information.
Include any theme or developer work needed to place the embed, test responsive layouts, and maintain the integration. A hosted viewer handles publishing and delivery, but that does not mean every storefront customization has zero implementation cost. Keep capture control software, hosted viewer subscriptions, and hardware purchases as distinct decisions.
Build a small pilot before forecasting the catalog
Choose a representative product, including a difficult reflective item if those are common in your range. Record preparation and editing time, inspect zoom detail, and test the viewer on desktop and phone. Use measured production time and actual hosted usage to estimate the wider rollout.
A useful budget is setup and equipment + product count × measured labor per product + integration work + viewer subscription and any usage overage. Add your applicable shipping, tax, outside service costs, and reshoot contingency separately. The 14-day free trial requires no credit card and lets you test the viewer before selecting a paid plan.
Illustrative production worksheet
| Budget line | Example assumption | Illustrative subtotal |
|---|---|---|
| Preparation and capture | 20 products × 30 minutes = 10 hours; assumed labor cost $40/hour | $400 |
| Editing and quality control | 20 products × 45 minutes = 15 hours; assumed labor cost $40/hour | $600 |
| Production labor total | 25 hours at the illustrative labor cost above | $1,000 |
| Setup and equipment | Existing equipment or supplier quote | Add your actual cost |
| Storefront implementation | Developer estimate for your theme | Add your actual cost |
| Viewer and usage | Current /pricing terms plus measured usage | Budget separately |
This example covers labor for one sequence per product, not a guaranteed throughput. Add fixture cleanup, extra stills, reshoots, shipping, tax, and contingency where applicable. Keep recurring viewer costs separate from this production subtotal.
- Read the REST API workflow
- Read the viewer API documentation
- Confirm API entitlements and Enterprise terms with sales
Frequently asked questions
How much does SpinShot viewer software cost?
Use the pricing page for current Professional, Business, and custom Enterprise terms, billing options, and included usage. Keep the viewer subscription separate from photography labor and equipment in your budget.
Is photography or hardware included in the viewer subscription price?
Do not treat the viewer subscription as a photography-service or hardware quote. Budget capture, editing, equipment, and any integration work separately, and consult the hardware pages or sales for purchasing details.
What usage overage should I budget for?
Measure storage and delivery usage in a representative pilot, then compare them with the current pricing page. Do not assume a fixed cost per spin or estimate bandwidth from catalog size alone.
Can I test the viewer before paying?
Yes. The 14-day free trial requires no credit card. Use a representative sequence and your actual storefront to evaluate the publishing workflow before choosing a paid plan.