Embedding a 360 virtual tour on any website: iframe vs. script, sizing and the gotchas The team behind Prewalk, a browser-based 360° tour tool, published guidance on embedding panoramic virtual tours into real estate and architecture sites, recommending an iframe plus a small script for responsive sizing and fullscreen, with a fixed-height iframe as a fallback when platforms like Wix or Google Sites block scripts. The writeup covers aspect-ratio CSS, lazy loading, the xr-spatial-tracking permission for VR mode, two-finger touch navigation, and CSP frame-src and host-side domain allow-listing as the usual causes of "Refused to connect" errors. Real estate and architecture sites increasingly put a walkable 360° tour right on the listing page instead of linking out. Under the hood it's just an iframe, but there are a few decisions that decide whether it feels native or broken. This is what we've learned building embeds for Prewalk https://prewalk.co , a browser-based 360° tour tool, but most of it applies to any panorama viewer. Iframe + a small script the nicer option Iframe only, fixed height the fallback