private-browser-ide.landing Open editor

site/private-browser-ide

Build full web apps & sites, in your browser

A real React, Vue, Angular, Svelte or TypeScript project normally needs a machine, a Node install, npm install, a dev server and, online, a cloud container and an account. XCODX Studio replaces all of it with one browser tab: your files are compiled, resolved, version-controlled and previewed on your own device, and never uploaded.

servernone
node.jsnone
accountnone
uploaded0 bytes
how-it-runs.jsonbrand-facts.json
{
  "runs_in": "your browser tab",
  "server": null, "container": null,
  "node_js": null, "npm_install": null,
  "account": null, "api_keys": null,
  "compilers": "Web Worker, this tab",
  "packages": "import maps, no node_modules",
  "git": "isomorphic-git, local",
  "storage": "IndexedDB on this device",
  "bytes_uploaded": 0,
  "works_offline": true,
  "price": 0
}
0 bytes uploaded · compilers idle · storage: this device

00 Live proof

This editor is running in your tab right now

No server built this. Edit app.js, press Run, and the page beside it recompiles and re-renders on your device. Open DevTools and watch the network: nothing carries your source anywhere.

01 tools

Every developer tool on xcodx.io

One private, browser-only engine powers the whole site. Each tool below is a different door into it, and each opens with nothing to boot.

02 no machine

Everything a project needs, without the machine it used to need

To our knowledge, XCODX is the first full-project browser IDE that builds, runs and previews a multi-file framework project with no server, no Node runtime, no container and no account. Here is what each piece of the traditional setup became.

  • A machine you control → any browser, any device

    Toolchains, permissions and a terminal used to need your own computer. Now it is a tab on a desktop, tablet, phone, Chromebook or a locked-down work laptop.

  • Node.js + npm install → a Web Worker and an import map

    Compilers and bundlers are Node programs and packages live in node_modules. XCODX compiles in a worker in your tab and resolves npm through browser import maps. No node_modules, no install step.

  • A dev server → a sandboxed preview fed from your tab

    Something has to serve compiled files and reload the page. Here it is an isolated preview origin served by a service worker inside your browser, with hot updates as you type.

  • A cloud container or VM → none

    Online IDEs boot a workspace on their servers to run your project. XCODX has no workspace to boot, queue for or pay for. Nothing runs on XCODX servers.

  • An account → none

    A server-side workspace needs an owner. Your projects live in your browser's storage, and you export them as a zip or a portable .xcodx file whenever you like.

  • API keys and secrets → none to expose

    Cloud IDEs hold credentials to run and share your work. XCODX has no backend holding your code or keys, so there is nothing to leak.

03 pipeline

What happens inside the tab

Six stages, all client-side, all ordinary browser code. Nothing below leaves your device.

  1. Edit

    Monaco, the engine behind VS Code, with IntelliSense, multi-cursor, Vim and Emacs modes, Prettier and a command palette.

  2. Compile

    TypeScript and JSX/TSX via Sucrase, Vue SFCs via @vue/compiler-sfc, Angular JIT, Svelte, SolidJS, SCSS/Sass via Dart Sass, Less, Pug and Tailwind, in a Web Worker.

  3. Resolve npm

    Bare imports such as import React from "react" map to versioned ESM builds through an import map. Only public package code is fetched from a CDN; your code is not sent anywhere.

  4. Version

    Real Git in the browser with isomorphic-git: stage, commit, branch, full history, offline. Plus per-file history with restore points.

  5. Preview

    Files stream from your tab into a sandboxed frame on a separate origin over a browser message channel, served by a service worker there. Full-width, split, device frames or a new tab.

  6. Audit

    Lighthouse-style audits for performance, accessibility, SEO and best practices, with jump-to-source for every finding, plus the device emulator.

04 privacy

100% private by architecture, not by policy

Most privacy promises are a policy: a company says it will not look at your code. XCODX's promise is structural. There is no backend that could.

The editor has no backend that receives, builds or stores projects, so there is nothing to look at. Your projects are stored locally in your browser's IndexedDB, your Git history is local, and the live preview is rendered from your tab. Close the tab and nothing of yours remains on any XCODX server, because nothing was ever there.

There is no account, so there is no credential to phish or leak. There are no API keys, because XCODX does not hold keys on your behalf; if your app needs one, it stays inside your project on your device. The preview runs on a separate, sandboxed origin, so preview code cannot reach the editor or your other tabs. Installed as a Progressive Web App, the editor, the compilers, Git and your projects keep working with no connection at all.

storage
IndexedDB on this device · export .zip / .xcodx
preview
isolated origin, service worker in your browser
account
none · no API keys · no login
offline
installable PWA
facts
same values in brand-facts.json
The one exception, stated plainly. Running non-web languages (Python, Java, C, C++, Go, Rust and 60+ more from the online compiler) cannot happen natively in a browser. When you press Run on such a file, that file's source is sent to XCODX's self-hosted execution service and the output is returned. Your project as a whole is still never uploaded, and no account is needed.
my-app — network log
  • open project my-app
  • 14 files loaded from IndexedDB · 0 requests
  • save src/App.tsx
  • sucrase: tsx → js 5ms (worker, this tab)
  • import map: react@19 · zustand@5 (public CDN, package code only)
  • preview: 14 files streamed to the sandbox over a MessageChannel
  • git commit -m "cart"
  • [main 7c2e1a9] cart · stored locally
  • requests carrying your source: 0

05 features

The full feature inventory

Everything XCODX Studio ships today, grouped the way the editor is organised. This is the reference list; the Help Center documents each item.

  • Editor engine

    • Syntax highlighting for 70+ languages, IntelliSense-style completion, signature help
    • Multi-cursor, column selection, select next occurrence, find and replace with regex
    • Command palette (Ctrl+Shift+P), minimap, code folding, bracket matching, linked tag editing
    • Error Lens inline diagnostics, problem badges on tabs, Outline panel
    • Light and dark themes, Zen mode, full-screen, split editors, tabbed multi-file editing
    • Vim and Emacs modes, Prettier format-on-save, screencast mode, cursor-centering, every Monaco option searchable in Settings
  • Runtime compiler

    • TypeScript, JSX and TSX via Sucrase
    • Vue single-file components via @vue/compiler-sfc
    • Angular JIT, including modern signal APIs
    • Svelte, SolidJS, Preact, Lit, Alpine.js, HTMX
    • SCSS/Sass and Less via Dart Sass with cross-file @use / @import / @forward and npm stylesheets; Pug to HTML; Tailwind
    • Vite-style projects: aliases, env vars, public assets; CommonJS modules bridged to ESM
  • npm packages

    • Search and add packages by name, pick a version
    • Smart auto-installer offers a package the moment you import it
    • Resolved through import maps and versioned ESM builds
    • Framework singletons kept (one React, one Angular core) across every dependency
    • Package stylesheets and fonts resolved for UI kits like Vuetify, Bootstrap and Ant Design
  • Source control

    • Powered by isomorphic-git: stage, commit, branch, browse full history
    • Works offline; the repository is stored with the project
    • Drive Git from the Source Control panel or the terminal
    • Git history travels with the portable .xcodx export
  • Terminal and console

    • Integrated terminal: run the preview, manage npm packages, drive Git
    • Live console with console.log / warn / error piped from the running preview
    • Execute the active file in 70+ languages with real stdin
    • Find in All Files across the whole workspace with jump-to-match
  • Preview and emulator

    • Instant hot preview as you type; Run / Reload on Ctrl+Enter
    • Full-width, split beside the editor, or in a new tab with client-side routing, forms and history
    • Pro device emulator with real phone, tablet and desktop frames
    • Sandboxed on an isolated origin, served by a service worker in your browser
  • Lighthouse audit lab

    • Performance, accessibility, SEO and best-practice audits, about 88% of real Lighthouse
    • Every finding links to the exact element and source line, across HTML, React, Vue, Svelte and Angular
    • Auto re-audit when the preview repaints
  • Projects, files and history

    • Multi-file workspaces with folders; many projects side by side, instant switching
    • Auto-save to IndexedDB; per-file history with restore points; auto-snapshot on Run
    • Import a .zip, a folder or single files by drag and drop
    • Export a standard .zip or a portable .xcodx file with settings and Git history
    • Export and import editor settings as JSON
  • Templates and playgrounds

    • 100+ starters: React, Vue, Angular, Svelte, SolidJS, Phaser, HTMX, Vite and more
    • UI kits pre-wired: Vuetify, Ant Design, shadcn/ui, MUI, Chakra, Mantine, Bootstrap
    • State and utility libraries: jotai, xstate, valtio, valibot, Zod, GSAP, D3, Three.js
    • 90+ dedicated framework playground pages under /build
  • Docs, notebooks and content

    • Markdown preview with GitHub-flavoured tables, task lists and alerts
    • Jupyter notebook (.ipynb) rendering: code, stdout, stderr, HTML and image cells
    • Mermaid diagrams and KaTeX math, theme-aware, with scroll sync
  • Platform, privacy and offline

    • Installable Progressive Web App; works offline once loaded
    • No account, no sign-up, no API keys, no telemetry of your source
    • Projects never uploaded; the only off-device step is the optional language runner
    • Runs on any modern browser: desktop, tablet, phone, Chromebook, locked-down machines
  • Embed on your site

    • Drop a live, runnable editor into any page: <iframe src="https://xcodx.io/playground/lite">
    • Preload your own files, control it from the host page with postMessage
    • Sandboxed, resizable, and a one-click hand-off to the full Studio

06 comparison

48 parameters: XCODX vs StackBlitz, vscode.dev and OneCompiler

Online IDEs are not all the same. The question that matters is where your project actually runs, and what it costs you in accounts, uploads and waiting. Every parameter across access, architecture, frameworks, tooling, languages, editor, workspace, preview and sharing.

fully supported partial or conditional not offered
48-parameter comparison of XCODX Studio, StackBlitz, vscode.dev and OneCompiler
ParameterXCODX Studio (xcodx.io)StackBlitzvscode.devOneCompiler
Access & cost
01No account or sign-upYes: Never — nothing to sign up forPartial: Open or fork without an account; sign in to saveYes: No accountPartial: Run without an account; sign in to save
02PriceYes: Free, no usage limits, no credit cardPartial: Free tier; paid plans for teams and boostsYes: FreePartial: Free with ads; paid tier
03Install or local toolchainYes: NoneYes: NoneYes: NoneYes: None
04Time to first runYes: Immediate — the project opens already runningPartial: Short WebContainer boot per workspaceNo: Cannot run — editor onlyYes: Instant (on their server)
05Phone and tablet useYes: Responsive UI, installable PWAPartial: Desktop-firstPartial: Desktop-firstPartial: Mobile app / simple pages
06Installable PWA, works offlineYes: Full PWA: editor, compilers, Git and projects offlinePartial: Partial offline cachingPartial: Partial offline cachingNo: Connection required
Architecture & privacy
07Where the project builds and runsYes: Your browser tab — compilers in a Web WorkerPartial: Your tab, inside a Node-in-WASM WebContainer (Chromium-class browsers)No: No build or runNo: Remote execution server
08Server or container behind a web projectYes: None — no backend receives, builds or stores projectsPartial: No container for running; a cloud workspace for savingYes: NoneNo: Every run goes to a server
09Your code uploaded to the vendorYes: NeverPartial: Yes, when a project is saved to your accountYes: No — local folder or GitHubNo: Yes, on every run
10Where projects are storedYes: Locally in your browser (IndexedDB)Partial: Cloud workspace on your accountYes: Local disk or GitHubPartial: Cloud, on your account
11API keys or credentials held by the serviceYes: None — there is no backend for them to live inPartial: Account tokens and integrationsYes: Only your GitHub sign-inPartial: Account
12Isolated, sandboxed preview originYes: Separate origin served by a service worker in your browserYes: WebContainer originNo: No previewNo: No preview
13Secrets and env vars stay on your deviceYes: Live only inside your local projectPartial: Stored with the cloud projectYes: LocalNo: Sent with the run
Frameworks & in-browser compilation
14React and Preact (JSX / TSX)Yes: Compiled in-browser with SucraseYes: Via WebContainer toolchainNo: Editing onlyNo: Plain HTML/JS only
15Vue single-file componentsYes: @vue/compiler-sfc in-browserYes: Via toolchainNo: Editing onlyNo:
16AngularYes: JIT compiled in-browser, signals supportedYes: Via Angular CLI in WebContainerNo: Editing onlyNo:
17Svelte and SolidJSYes: Compiled in-browserYes: Via toolchainNo: Editing onlyNo:
18Lit, Alpine.js, HTMX, jQueryYes: Ready-made playgroundsYes: Via npmNo: Editing onlyPartial: CDN script tags in plain HTML
19Vite-style projects (aliases, env vars, public/)Yes: Resolved in-browser, no Vite processYes: Real Vite in WebContainerNo: No:
20TypeScriptYes: Transformed in-browserYes: Via toolchainPartial: Editing and type hints, no runPartial: Runs on the server
21SCSS / Sass, Less, Pug, TailwindYes: Dart Sass in-browser, Less, Pug and TailwindYes: Via project toolingNo: Requires a local CLINo: Plain CSS only
22UI kits (MUI, Ant Design, Chakra, Vuetify, shadcn/ui…)Yes: Ready-to-run templatesYes: Via npmNo: No:
Packages & tooling
23npm packagesYes: Import maps — no node_modules, no install stepYes: Full npm install in WebContainerNo: No npm resolutionPartial: Fixed pre-installed libraries
24Package search and auto-installYes: Smart auto-installer offers a package when you import itYes: Package manager in terminalNo: No:
25Git source controlYes: Real local Git (isomorphic-git): stage, commit, branch, history, offlineYes: GitHub syncYes: Native source controlNo: No Git
26Terminal / shellYes: In-browser shell over your project filesYes: Real Node.js terminalNo: No terminalNo: Output panel only
27Node.js server code (Express, APIs)No: Front-end pipeline; server scripts run via the language runnerYes: Runs Node servers in the tabNo: Partial: Runs Node scripts, not servers
28VS Code extensionsNo: No extension marketplacePartial: LimitedYes: Web extensionsNo:
Languages & execution
29Programming languages you can runYes: 70+ (Python, Java, C, C++, Go, Rust, Ruby, PHP…), one page eachPartial: JavaScript, TypeScript and Node.js focusNo: No executionYes: 70+ languages
30Interactive stdinYes: Real stdin in the terminalYes: Node process.stdinNo: Yes: Supported
31Console piped from the running appYes: console.log / warn / error live in the editorYes: Terminal and browser consoleNo: Browser DevTools onlyYes: Output console
32Rich run output (tracebacks, images)Yes: stdout, stderr, images and tracebacksPartial: Text outputNo: Partial: Text output
Editor
33Code editor engineYes: Monaco — the engine behind VS CodeYes: Monaco / VS Code-basedYes: Official VS Code for the WebPartial: Basic editor
34IntelliSense, autocomplete, multi-cursor, command paletteYes: All built in, 70+ languagesYes: Built inYes: Built inPartial: Basic
35Vim and Emacs modesYes: Built in, one togglePartial: Via settings or extensionPartial: Via extensionNo:
36Prettier format-on-saveYes: Built inYes: Via project toolingPartial: Via extensionNo:
37Find in all files, Error Lens, linked tag editing, screencast modeYes: All built inPartial: Some, via VS Code featuresPartial: Via extensionsNo:
Workspace & files
38Multi-file projects with folders, many projects side by sideYes: Unlimited local projects, instant switchingYes: Cloud projectsYes: Local foldersPartial: Limited multi-file
39Per-file history, restore points, auto-snapshot on RunYes: Built in, stored with the projectPartial: Through GitPartial: Local historyNo:
40Import and exportYes: .zip and portable .xcodx (files, settings and Git history); drag in zips, folders or filesYes: Download as zipYes: Direct save to diskPartial: Single file download
41Ready-to-run templatesYes: 100+ starters and 90+ framework playgroundsYes: Many startersNo: Partial: Language samples
Preview, testing & audits
42Live hot preview as you typeYes: Instant — hot updates, no server round-tripYes: Fast HMRNo: No previewPartial: Static run
43Device emulator (phone, tablet, desktop frames)Yes: Pro emulator with real device framesNo: No: No:
44Lighthouse-style audits with jump-to-sourceYes: Performance, accessibility, SEO, best practices; ~88% of real LighthouseNo: No: No:
45Preview in a new tab with client-side routingYes: Full navigation, links, forms, historyYes: Preview URLNo: No:
Content & sharing
46Markdown, Jupyter notebook, Mermaid and KaTeX previewYes: Built in, theme-aware, scroll-syncedNo: Partial: Markdown built in; notebooks via extensionNo:
47Embed a live editor in your own siteYes: One iframe, free, no signup, no API key, preloadableYes: Via SDKNo: No iframe embedPartial: Single-file embed
48Real-time collaborationNo: Single-user by design — nothing leaves your devicePartial: With an accountPartial: Live Share extensionNo:

XCODX values describe the current release and are the same facts published in brand-facts.json. Competitor columns summarise each product's public documentation as of September 2026 and are offered in good faith; if something is out of date, write to [email protected] and it will be corrected. Longer write-ups: XCODX vs Replit and the comparisons section.

07 languages

Everything the editor understands

Syntax highlighting and IntelliSense cover 70+ languages. These are the ones XCODX also compiles in your tab or executes for you.

Compiled in your browser13

Zero build step. The transform runs on a Web Worker in your tab, so typing never blocks and nothing is uploaded.

  • JSX
  • TSX
  • TypeScript
  • Vue SFC
  • Svelte
  • Angular (JIT)
  • SolidJS
  • SCSS
  • Sass
  • Less
  • Pug
  • Tailwind
  • CommonJS → ESM

Rendered natively9

Straight to the live preview, no transform in the way.

  • HTML
  • CSS
  • JavaScript
  • JSON
  • Markdown
  • Jupyter (.ipynb)
  • Mermaid
  • SVG
  • YAML

Executed on demand22

70+ languages run through the self-hosted execution service, the only step that sends a single file off your device. stdout, stderr, images and tracebacks land in the console.

  • Python
  • Java
  • C
  • C++
  • C#
  • Go
  • Rust
  • Ruby
  • PHP
  • Kotlin
  • Swift
  • Lua
  • Scala
  • Perl
  • Haskell
  • Elixir
  • Dart
  • R
  • Julia
  • SQLite
  • Bash
  • PowerShell

08 questions

Private browser IDE — common questions

Does XCODX need a server to run my project?

No. For web projects — HTML, CSS, JavaScript, TypeScript, React, Preact, Vue, Angular, Svelte, SolidJS, Lit, Alpine.js, HTMX and Vite-style projects — every step runs inside your browser tab: compiling, resolving npm packages, Sass, Git and the live preview. XCODX has no backend that receives, builds or stores your project.

Do I need to install Node.js or npm?

No. TypeScript, JSX/TSX, Vue single-file components, Angular, Svelte, SolidJS, SCSS/Sass, Less and Pug are compiled by in-browser compilers running in a Web Worker, and npm packages are resolved through browser import maps. There is no node_modules folder and no npm install step.

Is my code private? Is anything uploaded?

Projects are stored locally in your browser (IndexedDB) and are never uploaded to XCODX servers. The live preview runs in a sandboxed frame on a separate origin, fed from your tab and served by a service worker in your own browser. The one exception is the optional 70+ language runner: pressing Run on a Python, Java, C++ or similar file sends that file's source to the self-hosted execution service and returns the output.

Do I need an account or an API key?

No. XCODX is free with no sign-up, no login and no API keys. Because there is no backend holding your projects, there are no credentials or secret keys that could be leaked.

Does it work offline?

Yes. Installed as a Progressive Web App, the editor, the in-browser compilers, Git and your locally stored projects keep working without a connection. Only fetching a new npm package from the CDN, and the 70+ language runner, need the network.

How is XCODX different from StackBlitz, CodeSandbox or Replit?

Cloud IDEs typically run your project in a container, a virtual machine or a browser-hosted Node runtime, and usually need an account to save. XCODX runs the whole pipeline as ordinary client-side code in one tab, with no runtime to boot, no account and nothing uploaded. Open a link and the project is already running. See the 48-parameter comparison on this page.

What can I build and preview entirely in the browser?

Multi-file projects in HTML, CSS, JavaScript and TypeScript; React, Preact, Vue, Angular, Svelte, SolidJS, Lit, Alpine.js and HTMX; Vite-style projects with aliases, env vars and public assets; SCSS/Sass, Less, Tailwind and Pug; UI kits such as Vuetify, Bootstrap, MUI, Ant Design, Chakra UI, Mantine, PrimeReact and shadcn/ui; plus Lighthouse-style audits and a device emulator.

Which developer tools does xcodx.io include?

The full Studio editor (/editor), 90+ framework and library playgrounds (/build), an online compiler with one page per language for 70+ languages (/compiler), the embeddable Lite editor (/playground/lite), the device emulator (/emulator), the Lighthouse audit lab (/lighthouse), 100+ templates, the Help Center (/help), the embedding guide (/documentation) and the developer blog (/blog).

How do I start a project in one click?

Open the editor and pick one of 100+ templates, or open a framework playground such as React, Vue, Angular or Svelte. The project opens already compiled with a live preview, and you can import an existing project as a zip, a folder or a portable .xcodx file.

Can I move my project somewhere else later?

Yes. Export any project as a standard .zip with its folder structure intact, ready to open in VS Code or deploy, or as a portable .xcodx file that also keeps your settings and Git history. Nothing is locked in.