# NitroIDE — full context for LLMs > Version: 2026-11-10 (v30.5). This file is updated on every release. > NitroIDE is a free, open-source, client-side browser IDE. Write HTML, CSS, and JavaScript with the Monaco editor, see live preview with hot module replacement, inject CDN libraries, and export your project as a ZIP — no account, no installation — your code runs only in your browser. ## Scope (important) - Frontend-only: HTML, CSS, and JavaScript. No Node.js, no backend, no database. - NitroIDE cannot run server-side code, host APIs, or replace CodeSandbox/Replit-style backends. - What it is for: instant frontend coding, prototyping, learning, demos, and shareable snippets. ## Pricing - 100% free, no account required, no paywall. Free forever — the only plan. - The AI pair programmer uses your own provider API keys — Groq, Gemini, and OpenRouter offer free tiers; NitroIDE charges nothing for AI. See https://nitroide.com/pricing.md ## What's new in v30.5 (October 2026) - Listed on 9 software directories (DevHunt, AlternativeTo, SaaSHub, SourceForge, directree, IndieTools, Fazier, NoLogin, TinyShelf) with a redesigned homepage badge row. - Daily publishing across X, LinkedIn, Peerlist, Hashnode and Coder Legion, mirrored on the Ecosystem Pulse page; blog library now 46 articles. - Trust and support: Trustpilot profile with public reviews, Ko-fi donations live, GitHub Sponsors approved. - Whole-site light-mode readability: light values for brand and code colors, fixed contact inputs, palette, footer, modal and stop-button contrast, dark variants for all article accent colors. - Deep audit pass (68 files): sitemap trimmed to 91 URLs in the Oct 31 audit pass; now 97 URLs, RSS fixed, icon fonts cut from 403KB to 19KB, service worker and forms hardened. - Directory badges fixed after a browser-isolation header blocked cross-origin images (header now credentialless, WebContainer WASM unaffected). - Templates "Open in NitroIDE" buttons readable in both themes. ## AI pair programmer (new in v30, October 2026) - Built-in AI pair programmer: a conversational chat in a right-hand sidebar inside the IDE workspace. - Bring your own key (BYOK): works with Groq, Gemini, OpenRouter, OpenAI, and SambaNova (via a non-storing proxy). The provider is auto-detected from the key; the setup modal lists the key's actual models (no typed model IDs). - Privacy: for Groq, Gemini, OpenRouter, and OpenAI, the browser talks directly to the chosen AI provider. SambaNova passes through a non-storing Cloudflare Worker proxy. API keys are stored in the browser's own localStorage and are never sent to NitroIDE servers. - Smart file selection: the AI sees the attached files (index.html, style.css, script.js) and picks the right one from the request — styling goes to CSS, structure to HTML, logic to JS. - Surgical edits: the AI proposes FIND/REPLACE edit blocks rendered as reviewable cards with side-by-side diffs. Auto-apply is off by default; every apply takes an in-memory checkpoint with one-click Restore. Ambiguous or unknown edit targets are refused rather than guessed. - Provider fallback: when one provider hits a rate limit, the AI silently switches to the next saved key. ## Privacy - Your code runs only in your browser and is never sent to NitroIDE servers. - Analytics is Google Analytics 4 only (loads for every visitor; page addresses are sanitized to path + utm_* params); no other telemetry. - Contact/feedback forms go to a Cloudflare Worker that emails the operator via Resend. Newsletter uses Buttondown. Share links compress the workspace into the URL itself (?code=) — nothing is uploaded. - See the privacy policy: https://nitroide.com/legal.html#privacy ## Offline - Works offline after first load (PWA + service worker). ## Sharing and embedding - Sharing: the Share button generates a `?code=` link containing the compressed workspace. - Embedding: append `?embed=1` to the workspace URL for a chromeless embed. - Import: `?gist=` loads a GitHub Gist, `?url=` imports a raw file, `?template=` loads a starter template. - API: `Nitro.watch(name, data)` renders a live, syntax-highlighted JSON tree of any watched value in the IDE's State tab. See https://nitroide.com/docs.html ## Templates (12) - portfolio — Personal Portfolio: https://nitroide.com/templates/portfolio.html - landing-page — Startup Landing Page: https://nitroide.com/templates/landing-page.html - css-art — Pure CSS Sunset: https://nitroide.com/templates/css-art.html - mini-game — Target Tap Game: https://nitroide.com/templates/mini-game.html - tailwind-demo — Tailwind via CDN: https://nitroide.com/templates/tailwind-demo.html - react-counter — React 18 Counter: https://nitroide.com/templates/react-counter.html - todo-app — Todo App: https://nitroide.com/templates/todo-app.html - clock — Analog + Digital Clock: https://nitroide.com/templates/clock.html - gradient-generator — CSS Gradient Generator: https://nitroide.com/templates/gradient-generator.html - markdown-preview — Markdown Previewer: https://nitroide.com/templates/markdown-preview.html - countdown — Countdown Timer: https://nitroide.com/templates/countdown.html - link-in-bio — Link in Bio: https://nitroide.com/templates/link-in-bio.html - Full list: https://nitroide.com/templates.html — community templates can be submitted via a ?gist= / ?url= share link. ## Key pages - NitroIDE home: https://nitroide.com/ — product overview and live editor - Open workspace: https://nitroide.com/tools/codebox.html — the browser IDE itself - Templates: https://nitroide.com/templates.html - Docs: https://nitroide.com/docs.html — embed, import, API reference - Ecosystem Pulse: https://nitroide.com/ecosystem.html — recent builds, logs, and live activity - Blog: https://nitroide.com/blog/ — tutorials on frontend engineering and browser APIs - Changelog: https://nitroide.com/changelog.html - Contact: https://nitroide.com/contact.html — report bugs, request features, or say hello - About: https://nitroide.com/about.html — about NitroIDE and the story behind the engine - Cheatsheet: https://nitroide.com/cheatsheet.html — keyboard shortcuts and quick reference - Roadmap: https://nitroide.com/roadmap.html — what has shipped and what is next - Showcase: https://nitroide.com/showcase.html — sites built with NitroIDE - Pricing: https://nitroide.com/pricing.md ## Landing pages - Code on Chromebook: https://nitroide.com/landing/chromebook-code-editor-free.html - CodePen Alternative: No Login, Free IDE: https://nitroide.com/landing/codepen-alternative-no-login.html - Lightweight CodeSandbox Alternative: https://nitroide.com/landing/codesandbox-lightweight-alternative.html - Export HTML, CSS & JS to ZIP: https://nitroide.com/landing/export-code-to-zip.html - HTML, CSS & JS Editor: https://nitroide.com/landing/html-css-js-editor.html - JSFiddle Alternative with Monaco Editor: https://nitroide.com/landing/jsfiddle-alternative.html - Best Low RAM Code Editor: https://nitroide.com/landing/low-ram-code-editor.html - Monaco Editor Online: https://nitroide.com/landing/monaco-editor-online.html - Free Offline HTML Editor: https://nitroide.com/landing/offline-html-editor.html - Secure Private Code Editor: https://nitroide.com/landing/private-code-editor-no-tracking.html - React Online Playground: https://nitroide.com/landing/react-online-playground.html - Free Replit Alternative: https://nitroide.com/landing/replit-alternative-free.html - Responsive Design Tester: https://nitroide.com/landing/responsive-design-tester.html - Run React in Browser: https://nitroide.com/landing/run-react-in-browser-no-install.html - Lightweight StackBlitz Alternative: https://nitroide.com/landing/stackblitz-lightweight-alternative.html - Tailwind CSS Online Editor & Playground: https://nitroide.com/landing/tailwind-online-editor.html - Test Tailwind CSS Online: https://nitroide.com/landing/test-tailwind-css-online.html - Vanilla JavaScript Sandbox: https://nitroide.com/landing/vanilla-javascript-sandbox.html - Best VS Code Online Alternative: https://nitroide.com/landing/vscode-online-alternative.html - CodeSandbox vs NitroIDE: https://nitroide.com/landing/codesandbox-vs-nitroide.html - CodePen vs CodeSandbox: https://nitroide.com/landing/codepen-vs-codesandbox.html ## Articles - The Codebox Engine: How Editor, Preview and Console Stay in Sync Without a Server: https://nitroide.com/blog/codebox-engine.html - Privacy as a Feature: Your Code Never Leaves Your Machine: https://nitroide.com/blog/privacy-as-a-feature.html - Embeds: Putting a Live NitroIDE Playground Inside Your Docs: https://nitroide.com/blog/embeds-live-playground-in-docs.html - JSON-LD Recipes: BlogPosting, FAQPage, SoftwareApplication: https://nitroide.com/blog/json-ld-recipes-no-plugin.html - SEO Checklist: Sitemap, Schema, and llms.txt | NitroIDE: https://nitroide.com/blog/seo-checklist-for-indie-hackers.html - Offline-First on GitHub Pages: What Works, Where It Ends: https://nitroide.com/blog/offline-first-github-pages.html - localStorage Is My Database: Patterns, Limits, Graduation: https://nitroide.com/blog/localstorage-as-database.html - I Built a Blog Engine With No Build Step | NitroIDE: https://nitroide.com/blog/vanilla-js-blog-engine.html - 12 Starters, Zero Blank Pages: Template Gallery Tour: https://nitroide.com/blog/templates-gallery-tour.html - Hardened Static Site: The Cloudflare Headers Recipe: https://nitroide.com/blog/cloudflare-security-headers-recipe.html - HMR Without a Bundler: How Instant Preview Updates Work: https://nitroide.com/blog/hmr-without-a-bundler.html - Nitro.watch(): A Live State Panel for My Browser IDE: https://nitroide.com/blog/state-watcher.html - No-Server IDE: Your Code Runs Only in Your Browser: https://nitroide.com/blog/no-server-architecture.html - NitroIDE AI Pair Programmer: Bring Your Own Key: https://nitroide.com/blog/ai-pair-programmer-byok.html - postMessage Sanitizer: A Recipe for Building iframe Tools: https://nitroide.com/blog/postmessage-sanitizer.html - I Published 91 Posts With 0 Followers. What the Numbers Say: https://nitroide.com/blog/91-posts-0-followers-lessons.html - I Replaced My Share Backend With a URL | NitroIDE: https://nitroide.com/blog/instant-code-sharing-zero-backend.html - How NitroIDE Renders Code Instantly: srcdoc + postMessage: https://nitroide.com/blog/0ms-preview-srcdoc-postmessage-no-bundler.html - CodeSandbox & StackBlitz Alternative: No-Cloud Frontend IDE: https://nitroide.com/blog/codesandbox-stackblitz-alternative-local-webcontainers.html - Web Workers & Multithreading: A Practical Guide | NitroIDE: https://nitroide.com/blog/web-workers-multithreading-browser-guide.html - Browser Storage: OPFS & IndexedDB | NitroIDE: https://nitroide.com/blog/browser-storage-offline-apps-opfs-indexeddb-guide.html - Browser Networking: Fetch, Streams & WebTransport | NitroIDE: https://nitroide.com/blog/browser-networking-fetch-streams-webtransport-guide.html - Modern CSS for App UIs: Houdini, Container Queries: https://nitroide.com/blog/modern-css-app-ui-houdini-container-queries-guide.html - Canvas & Web Audio: Creative Coding Guide | NitroIDE: https://nitroide.com/blog/canvas-webaudio-creative-coding-guide.html - WebAssembly in the Browser: What It Can (and Can't) Do: https://nitroide.com/blog/webassembly-browser-honest-guide.html - Browser Hardware APIs: Serial, Bluetooth, HID, USB & MIDI: https://nitroide.com/blog/browser-hardware-apis-serial-bluetooth-hid-guide.html - Browser Performance: Scheduler & Memory | NitroIDE: https://nitroide.com/blog/browser-performance-scheduler-observers-memory-guide.html - Browser Security: WebCrypto & Sandboxing Patterns | NitroIDE: https://nitroide.com/blog/browser-security-webcrypto-sandboxing-guide.html - Prototype React, Vue & TypeScript — No Build Step | NitroIDE: https://nitroide.com/blog/prototype-react-vue-typescript-browser-cdn-guide.html - Vim & Emacs in the Browser: The Power User's Editor: https://nitroide.com/blog/vim-emacs-online-editor-keybindings.html - Migrate Your Monorepo to a Browser Workspace | NitroIDE: https://nitroide.com/blog/migrate-local-monorepo-browser-based-ide.html - Free Online IDE for Students and Bootcamps (2026) | NitroIDE: https://nitroide.com/blog/best-free-online-ide-students-bootcamps.html - The Most Advanced HTML, CSS, & JS Online Editor in 2026: https://nitroide.com/blog/html-css-js-online-editor-playground.html - Offline-First IDE: Code on an Airplane | NitroIDE: https://nitroide.com/blog/offline-first-browser-ide-pwa.html - Code Editor for iPad Pro: Frontend Coding on iOS: https://nitroide.com/blog/best-code-editor-ipad-pro-m4-browser-ide.html - Digital Nomad Coding Setup: 100% Offline Browser IDE: https://nitroide.com/blog/digital-nomad-coding-offline-browser-ide.html - Move a Project from Replit to NitroIDE (Manual Guide): https://nitroide.com/blog/migrate-replit-to-nitroide-tutorial.html - Free Online IDEs in 2026: An Honest Comparison | NitroIDE: https://nitroide.com/blog/best-online-ide-free-2026-comparison.html - OPFS vs IndexedDB: Zero-Trust AES-GCM Storage | NitroIDE: https://nitroide.com/blog/opfs-vs-indexeddb-virtual-file-system.html - Build React Apps Without npm | Browser AST Transpilation: https://nitroide.com/blog/how-to-use-react-without-npm.html - JIT Tailwind CSS Compilation in the Browser | NitroIDE: https://nitroide.com/blog/tailwind-css-in-browser-no-postcss.html - Zero-Latency Browser IDE Architecture | NitroIDE: https://nitroide.com/blog/zero-latency-local-browser-ide-architecture.html - An Honest Cloud9 Alternative for Offline Coding | NitroIDE: https://nitroide.com/blog/aws-cloud9-alternative-local-compute.html - Visualizing RxJS and Redux State in Real-Time | NitroIDE: https://nitroide.com/blog/rxjs-redux-state-visualization-ide.html - Real-Time Auto-Formatting via AST Manipulation | NitroIDE: https://nitroide.com/blog/ast-manipulation-auto-formatting-babel.html - Export to ZIP: From Browser Session to Deployed Site: https://nitroide.com/blog/export-to-zip.html ## Full article text ### The Codebox Engine: How Editor, Preview and Console Stay in Sync Without a Server Source: https://nitroide.com/blog/codebox-engine.html Date: November 2026 Every browser IDE has the same three panes: the editor on one side, the live preview on the other, and a console somewhere underneath. What users never see is the plumbing between them — and in a tool with no server, that plumbing has to do all the work a backend normally would. NitroIDE's codebox is three Monaco editor instances, one sandboxed iframe, and a console panel, all coordinated by a small engine that lives entirely in your browser. Here is how it actually works. ## Three editors, one workspace The workspace is three files — index.html, style.css and script.js — and each one gets its own Monaco instance. Monaco is the editor engine behind VS Code, so the typing experience is the real thing: syntax highlighting, bracket matching, Emmet, find and replace. But the interesting part is not the editing. It is that the three editors are treated as one source of truth: the engine reads their current contents whenever it needs to rebuild, and nothing about your code ever leaves the machine to do it. ## The preview is a document, not a page The live preview is an The embed loads a stripped-down, read-only viewer. The full IDE chrome is gone — no file explorer, no console panel, no settings menus. What remains is the two things a reader actually needs: the editor and the live preview, side by side. The reader sees the code and its output in the same frame, on the same page, with nothing to install and no account to create. Read-only is a deliberate choice, not a missing feature. A tutorial embed is not a workspace; it is a demonstration. If the reader could edit the code in place, every edit would be a fork of the author's example with no way back — and the next reader would see someone else's experiment, not the tutorial. So the embed shows, and the escape hatch handles editing: every embed carries a footer link reading "Built with NitroIDE — open & edit". One click opens the exact workspace in the full editor, where the reader can change anything. Show first, edit second, and never confuse the two. ## Where this actually belongs The honest answer is: anywhere that renders an iframe and where the reader is there to learn. Blog posts, documentation pages, tutorial sites, course material — anywhere a code sample currently sits as a dead block. It does not belong in a GitHub README. GitHub strips iframes from rendered Markdown, so an embed pasted into a README renders as nothing. That is what the "Open in NitroIDE" badge is for — a link, not a frame — and knowing which of the two a surface accepts is the difference between an embed that works and one that silently vanishes. If the page cannot render an iframe, do not force the embed in; link out instead. The second place it belongs is less obvious: your own changelog and release notes. A new feature described in prose is a claim; the same feature embedded as a running demo is evidence. When a release note says "the preview now updates without flicker," an embedded playground running the new behaviour lets the reader verify it in ten seconds instead of trusting the sentence. ## The details that make an embed feel native, not bolted on A bare iframe works. A few attributes make it feel like part of the page: None of these are NitroIDE features. They are the hosting page's job, and they are the difference between an embed that feels like part of the tutorial and one that feels pasted in. ## The limits, stated plainly An embed inherits every limit of the share link it is built on. The workspace travels inside the URL itself, compressed into the ?code= parameter, so a very large project makes a very long URL. For a tutorial demo — a handful of files, a single concept — that is never a problem. For a full application, it is: use ZIP export for the project and embed a small, focused demo of the idea instead. The embed is for the example, not the app. The second limit comes from the preview's sandbox. NitroIDE's preview runs in a sandboxed iframe with an opaque origin, which is what keeps code in a shared link from touching the reader's saved projects. The tradeoff is that localStorage, sessionStorage, and cookies are unavailable inside the preview — and in Safari, touching them throws a SecurityError. Demo code that reads localStorage unguarded will crash inside the embed while working fine in a normal tab. Wrap storage access in try/catch in any code you plan to embed, and the same demo runs everywhere. The third limit is the read-only viewer itself. It hides the console, so a demo whose point is console output — logging, errors, debugging — loses its punchline inside an embed. That is a real constraint, and the honest response is to pick the right surface: embed the demos whose output is visual, and link out to the full editor for the ones whose output lives in the console. ## Why this matters more than a nicer code block Syntax highlighting made code readable. Embeds make it runnable, and that is a different category of change. A readable sample asks the reader to trust the author. A runnable sample lets the reader check the author — change a value, watch the preview move, break it, fix it. That is the feedback loop NitroIDE is built around, except now it happens inside someone else's docs, for a reader who never opened the IDE at all. The embed is also the quietest distribution NitroIDE has. Every embed carries its own attribution in the footer, and every footer click is a reader who arrived at the full editor from inside a tutorial they were already reading — not from a post, not from an ad, from a working demo. That is the growth loop that does not look like a growth loop: make the tool useful inside other people's pages, and let the pages do the talking. One parameter, one iframe, one running demo where a dead code block used to be. Try it with the docs example above — paste a share code into the snippet, drop it into a page, and the tutorial stops describing the code and starts running it. ## Try it I build NitroIDE — a browser-based IDE where your code never leaves your machine: nitroide.com ⭐ If you enjoyed this, star NitroIDE on GitHub: github.com/nitroideofficial/nitroide ## Frequently asked questions ### How do you embed a NitroIDE playground in a page? Take any NitroIDE share URL, add ?embed=1 to it, and drop it in an iframe. It loads a stripped-down, read-only viewer with just the editor and the live preview — no file explorer, console panel, or settings menus. ### Why is the embed read-only? A tutorial embed is a demonstration, not a workspace. If readers could edit in place, the next reader would see someone else's experiment instead of the tutorial. The footer link "Built with NitroIDE — open & edit" opens the exact workspace in the full editor for anyone who wants to change it. ### Where should you not use a NitroIDE embed? GitHub READMEs strip iframes from rendered Markdown, so an embed there renders as nothing — link out with the "Open in NitroIDE" badge instead. And demos whose point is console output lose their punchline, because the embed hides the console; those belong in the full editor. --- ### JSON-LD Recipes: BlogPosting, FAQPage, and SoftwareApplication Without a Plugin Source: https://nitroide.com/blog/json-ld-recipes-no-plugin.html Date: October 2026 Two weeks ago I wrote the overview: a static indie site needs three machine-readable files — sitemap, schema, and llms.txt. That post told you what each one is for. This one is the part I left out on purpose: the actual code. I run NitroIDE, a browser IDE on a static host with no server, no build step, and no plugin system. There is no SEO plugin to install, so every block of structured data on the site is a