Hosting 3D Tours: Options, Costs and Embedding
Hosting 3D Tours: Options, Costs and Embedding
Hosting a 3D tour means keeping the finished tour files on a server that serves them to any viewer, on any device, through a link or an embed on your website. You have two routes: a provider’s platform that hosts the tour for a recurring fee, or your own web server or cloud storage that you manage. The right one depends on how many tours you run, how long they must stay live and who handles IT.
This guide is written for developers, architects, builders and marketing teams who commission tours rather than build them. It covers what hosting involves, how the two routes compare, which terms to read before you sign, how to embed a tour, and how to keep it working for years.
TL;DR
- Creating a tour and hosting it are separate jobs. Ask for both to be scoped in the quote, and ask who owns the files.
- Platform hosting is the fastest to launch. Self-hosting gives you control and a predictable cost for large or long-lived portfolios.
- Before you commit, check storage caps, how many tours stay active, what happens if you stop paying, and whether you can export your files.
- Embedding is usually one snippet pasted into a page. Test it on a phone before you publish.
- Plan for the long term: keep an archive of source files, review links yearly and keep access controls current.
Table of Contents
- What hosting a 3D tour actually involves
- Two ways to host: provider platform or your own server
- What to check before you choose: costs, storage and access terms
- Speed and device compatibility
- How to embed a hosted tour and share it
- Keeping a tour accessible and secure over the years
- Our perspective: ask for the hosting plan with the visualization
- Getting a hosted tour built for your project
- A practical decision path
- FAQ
- Sources
What hosting a 3D tour actually involves
A 3D tour is a set of files: images or rendered frames, 3D geometry or panoramas, hotspot data and a viewer that stitches them into something a visitor can move through. Creating the tour produces those files. Hosting is everything that happens after: storing them, delivering them quickly to a browser, giving them a stable web address and keeping them available.
That distinction matters when you hire a studio. A quote for a tour can mean a finished file package handed to you, a link to a tour on the studio’s chosen platform, or both. If the tour lives on a platform account, find out whose account it is. If the account lapses, the link usually goes dead, and so does every brochure, listing and email that points to it.
For a developer selling units off plan, the tour might be live for two to five years, from pre-sales through handover. For an architect, it may be a client review link that only needs to work for three weeks. Those two cases call for very different hosting decisions.
Tours made from renderings vs. captured tours
Two kinds of tour exist, and they host differently. A captured tour is built from photos or scans of a finished building. A rendered tour is built from a 3D model of a building that does not exist yet. Pre-construction projects, which is where most of our work sits, are rendered tours, so there is nothing to photograph and the files come entirely from the design team and the visualization studio. That gives you more freedom: a rendered tour is a deliverable you can store, move and republish. You can see the range of formats in our virtual tour examples.
Two ways to host: provider platform or your own server
Hosting on a provider’s platform
The studio or a platform vendor stores the tour and gives you a link and an embed code. You do not touch servers, security patches or bandwidth. Updates to the tour appear everywhere the link is used, which is handy when finishes or unit availability change.
The trade-off is the recurring fee and the dependency. Plans are typically priced by the number of active tours or by storage and traffic, and the tour stops being served if the subscription ends. Read the access terms (covered below) before you accept a platform as the default.
Self-hosting on your website or cloud storage
Self-hosting means the tour package sits on a web server you control, often behind a content delivery network (CDN). A CDN keeps copies of static files at edge locations near your visitors. AWS describes CloudFront as delivering cacheable static content from edge locations, and says that offloading static content to a CDN reduces the load on your main servers, so they can stay smaller and more efficient.
Self-hosting suits you when:
- You run many tours and per-tour platform fees would add up.
- The tour must stay online for years with no subscription risk.
- Your brand needs the tour on its own domain, with its own analytics.
- Your legal or IT team requires control over where data sits.
It does not suit you when nobody on your side can manage a server, a certificate renewal or a cache setting. In that case a managed route is safer than a broken link in front of a buyer.
Side-by-side comparison
| Factor | Provider platform | Self-hosted |
|---|---|---|
| Time to launch | Fast, link ready on delivery | Needs setup and testing |
| Who maintains it | The provider | You or your IT contractor |
| Cost pattern | Recurring, often by active tour or storage | Storage and bandwidth usage, plus setup |
| Control over domain and data | Limited by the platform | Full |
| Risk if payments stop | Tour may go offline | Tour stays up while your hosting is paid |
| Best for | A few tours, short campaigns | Large portfolios, long-lived projects |
Many teams land on a hybrid: a platform link for fast client reviews and a self-hosted copy for the permanent marketing site.
What to check before you choose: costs, storage and access terms
The headline price rarely tells the whole story. Put these questions to any provider, and to your own IT team if you self-host.
- What counts as an active tour? Some plans cap how many tours can be live at once. Archived tours may need to be reactivated, sometimes for a fee.
- What are the storage and traffic limits? High-resolution rendered tours are heavy. A launch-day email to thousands of buyers is a traffic spike.
- What happens when you stop paying? Ask whether the tour goes offline immediately, after a grace period, or stays in a read-only state.
- Can you export everything? You want the full package, not only a link. Without it, switching providers means rebuilding.
- Who owns the account and the files? The contract should say the files are yours, and that the account is in your company name or can be transferred.
- Is there a branded domain option? Your own address keeps your SEO value and survives a change of vendor.
- What are the privacy controls? Password protection or private links matter for pre-launch projects and investor reviews.
On cost, a CDN-based setup can start small. Amazon CloudFront lists flat-rate plans starting at $0 per month for hobbyists, scaling up for business needs, with no overage charges for the data allowance included (AWS, 2026). A commercial portfolio will land on a paid tier, and you should confirm the current plan terms on the AWS page, because they change.
Speed and device compatibility
A tour that stalls on a phone loses the buyer. The same visualization can feel instant or sluggish depending on how it is prepared and delivered. Three things drive most of the difference.
File weight. Texture sizes and polygon counts decide how much a browser must download and draw. Google’s web.dev case study on a WebGL experience found that using low-poly models and optimized texture sizes helps mobile performance, and that visual quality has to be balanced against speed.
Resolution scaling. The same case study notes that rendering the canvas at a lower resolution, such as 50%, and scaling it up with CSS is a way to keep mobile frame rates smooth. A good studio makes these calls for you, with a lighter version for phones and a richer one for desktop.
Delivery. Serving files from a CDN means a visitor in Miami and one in Seattle both load from a nearby location, not from one distant server.
When you brief a studio, ask for a mobile-first test on a mid-range phone, not only on the design team’s workstation. Many of your buyers will open the link from a text message or a social ad on a phone.
How to embed a hosted tour and share it
There are three common ways to put a tour in front of people.
- A direct link. Simple and reliable. Use it in emails, proposals and messages. A short, branded address is easier to trust than a long platform URL.
- An embed on your page. Most platforms and self-hosted packages give you an iframe snippet. You paste it into a page block on your site builder or CMS. A responsive embed resizes to the screen, while a fixed-size embed stays the same size on every device. Pick responsive unless the layout demands otherwise.
- A QR code or kiosk. For sales galleries and site hoardings, a QR code points to the tour link. Use a link you control so the code never has to be reprinted.
Embedding checklist
- Place the tour high on the page, with a clear preview image and a call to action beside it.
- Give the frame a sensible height on mobile, so visitors can still scroll past it.
- Confirm the page loads over HTTPS, or the browser may block the embed.
- Test on iPhone Safari, Android Chrome and a desktop browser.
- Add a text summary of the project near the tour, which helps visitors who cannot load it and gives search engines something to read.
For teams coordinating many stakeholders, sharing the right link with the right person matters as much as the tour itself. Clear review loops are part of construction client communication, and a single, stable tour link keeps feedback tied to the same version.
Keeping a tour accessible and secure over the years
A tour is a marketing asset that outlives the campaign. Treat it like one.
- Keep a master archive. Store the full delivery package, source model references and a written list of what each file is. Put it somewhere your company controls, not only in one person’s inbox.
- Own the domain and the account. Register the web address in the company name and keep renewal contacts current.
- Review links once a year. Click every tour link from your site, brochures and listing pages. Retire or redirect dead ones.
- Control access. Use password protection or private links for pre-launch phases and remove access when people leave the project.
- Keep software current. If you self-host on a CMS, apply security updates and renew your HTTPS certificate before it expires.
- Update the design status. When finishes, layouts or unit availability change, request revised scenes so the tour matches what is built. Outdated visuals create disputes at handover.
If the project ends in sale or handover, decide who inherits the tour. Writing that into the handover checklist avoids a lapsed subscription on a building that is still being marketed.
Our perspective: ask for the hosting plan with the visualization
We have completed more than 1,000 projects for architects, developers, builders and agencies, and the pattern is consistent: the visuals get all the attention at kickoff, and hosting gets decided the week before launch. That is the wrong order. The way a tour is delivered affects how it is built, because a tour meant for a phone-first audience is prepared differently from one shown on a sales-gallery screen.
Our approach is to scope the tour and its delivery together. We work with you from concept to final delivery, with feedback at each stage, so the format, file weight and the way you will share it are agreed while changes are still cheap. For walkthroughs, that means you know before production whether you will receive a link, a file package for your own server, or both.
We would also argue for owning your files. A visualization is an asset your team paid for. Having a complete package on your side means you can place it on your site, hand it to a sales partner or move it later without starting from scratch. Whether it lives on a platform, on your servers, or both, you should always be able to point to where the master copy is.
If you are planning a launch, bring us the audience, the channels and the expected lifespan of the project. We will help you decide what to build and how to deliver it.
, Rendimension
Getting a hosted tour built for your project
If you are weighing a new tour for a development, a listing or a sales gallery, we can scope the visualization and its delivery together. Published pricing starts at 850 USD per scene for architectural rendering, with additional camera views from 425 USD per view, and 3D walkthroughs priced from 4500 to 8000 USD. Other formats, including VR experiences and 360° virtual tours, are quoted per project.
See our 3D walkthrough services or the 360° virtual tours page, then request a quote with your audience, platforms and timeline. For agents who need tours for listings, our page on 3D walkthroughs for real estate agents shows how they are used. General contractors can see a related use case in 3D walkthroughs for general contractors.
A practical decision path
If the choice still feels open, use this short route.
- One or two tours, short campaign, no IT support: use a provider platform and make sure you receive the files at the end.
- A multi-unit development live for years: plan a self-hosted copy behind a CDN on your own domain, and keep a platform link for quick client reviews.
- Many projects across locations: self-host for volume and standardize your embed template, so each new project follows the same checklist.
- Private investor or board reviews: use access-controlled links and set an expiry date for access.
In every case, write down who owns the files, who pays for hosting, who renews the domain and who checks the links each year. Four names on a page prevent most hosting failures.
FAQ
What is the difference between creating and hosting a 3D tour?
Creating a tour produces the files: the scenes, the model and the interactive layer. Hosting stores those files on a server and delivers them to viewers through a link or embed. A studio can do one or both, so confirm in the quote exactly what you receive.
Do I need to host a 3D tour on my own website?
No. A provider platform can host it and give you a link or embed code. Your own hosting makes more sense when you manage many tours, need a branded domain or want the tour online without a subscription.
How do I add a 3D tour to my website?
Most hosts give you an iframe snippet that you paste into a page or custom block. Choose a responsive embed so it fits phones and desktops, make sure the page runs on HTTPS, and test it on several devices before launch.
What should I check about ongoing hosting costs?
Check how many active tours a plan allows, the storage and traffic limits, what happens if you stop paying and whether you can export all files. Ask for these terms in writing before the tour goes into your marketing.
Why does my 3D tour load slowly on a phone?
Heavy textures and complex models are the usual cause. Lighter models, optimized texture sizes and delivery through a CDN usually help. Ask your studio for a mobile-optimized version and test it on a mid-range phone.
Sources
- Amazon CloudFront pricing, plans and free tier (AWS)
- Amazon S3 and Amazon CloudFront: A Match Made in the Cloud (AWS)
- The Hobbit Experience (web.dev)