WebSandbox
FeaturesUse CasesEcosystemTestimonialsPricingFAQDocsBlogs
Getting Started · Installation & Setup
Getting Started
  • Introduction
  • Quick Start
  • Installation & Setup
Features
  • Code Editor
  • Live Preview
  • Terminal
  • Git Integration
Platform Guide
  • Dashboard
  • Workspaces & Projects
  • Settings & Preferences
  • Plans & Pricing
Advanced
  • How WebSandbox Works
  • WebContainers Explained
  • Cloud Servers Explained
  • Workspace Architecture
  • Performance & Caching
  • Security Model
DocsGetting StartedInstallation & Setup

Installation & Setup

Last updated: June 1, 2026

Browser requirements, network configuration, and optional desktop integration for WebSandbox.

Browser Requirements

WebSandbox requires a browser that supports the following platform APIs:

  • SharedArrayBuffer — required by WebAssembly threads (enabled automatically when the page is served with COOP/COEP headers)
  • Service Workers — used to intercept and route preview traffic from the in-browser dev server
  • IndexedDB — used to persist your workspace file system and git state across page refreshes
  • WebAssembly — the WebContainer runtime is compiled to WASM
BrowserMinimum VersionStatus
Google Chrome90+✓ Fully Supported
Microsoft Edge90+✓ Fully Supported
Mozilla Firefox90+⚠ Supported (minor quirks)
Safari16.4+⚠ Limited (no SharedArrayBuffer on iOS)

Network Requirements

WebSandbox requires an internet connection for the initial page load to download the WebContainer WASM binary. After the Service Worker is registered and the binary is cached, WebSandbox can run most operations offline.

The following domains must be reachable through your network or proxy:

  • websandbox.dev — main application
  • cdn.websandbox.dev — static assets and WASM binary CDN
  • registry.npmjs.org — for npm install inside workspaces
  • cors.isomorphic-git.org — CORS proxy for git remote operations

Service Worker Setup

WebSandbox automatically registers a Service Worker on first load. The Service Worker is responsible for:

  1. Serving the Cross-Origin-Embedder-Policy: require-corp and Cross-Origin-Opener-Policy: same-origin headers that unlock SharedArrayBuffer
  2. Intercepting preview traffic (requests to the in-browser dev server port) and routing them to the WebContainer network stack
  3. Caching the WASM binary and core assets for offline use

If you see a "Service Worker registration failed" error, ensure your browser is not in private/incognito mode, as some browsers restrict Service Workers in that context.

PWA Installation (Optional)

WebSandbox ships as a Progressive Web App. You can install it to your operating system for a native-like experience:

  • Chrome / Edge — Click the install icon in the address bar, or go to Settings → Install WebSandbox as an app
  • macOS — Use Safari's File → Add to Dock option

Once installed, WebSandbox opens in a standalone window without browser chrome and behaves like a native desktop IDE.

Enterprise Deployment Notes

If you are deploying WebSandbox access within a corporate network, ensure your content security policy and proxy allow the domains listed in the Network Requirements section above. Contact enterprise@websandbox.online for enterprise licensing, SSO configuration, and dedicated infrastructure options.

Have questions or need help? Join our Discord community.

On this page

WebSandbox

A real development environment. Entirely in your browser. Boot instant workspaces with WebContainers, or scale up with dedicated VS Code Servers.

GitHub
Twitter
LinkedIn

Product

  • Features
  • Use Cases
  • Ecosystem
  • Testimonials
  • Pricing
  • FAQ

Platform

  • Blogs
  • Changelog
  • Roadmap
  • Documentation
  • Community
  • System Status

Company

  • About us
  • Security
  • Subprocessors
  • Brand Kit
  • Acknowledgement
  • Support

Legal

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Acceptable Use
  • Data Processing
  • Licensing

© 2026 WebSandbox. All rights reserved.

Built with ❤️ by Ranit Manik

All systems operational