RawServe

RawServe is a lightweight, zero-hosting web importer designed to fetch and render raw HTML pages directly inside your browser. By resolving dependency paths natively on-the-fly, you can instantly test and display your files without deployment pipelines or CORS headaches.

1. Serving Remote Files

Copy any raw HTML URL (e.g., from a GitHub repository or GitLab snippets) and paste it into the Target HTML URL field in the Serve tab. Click Serve File to render it instantly.

2. Using Different CDNs

GitHub Raw URLs enforce a strict plain text MIME type restriction. Under the hood, RawServe bypasses this using CDN proxies:

• GitHack (Recommended): Directly routes requests and maps correct MIME headers so CSS and JS execute instantly.
• jsDelivr: An alternative CDN for public repository asset distribution.

3. Offline Local Sandbox

To safely test and execute local code without setting up a localhost environment, click on Choose File / Browse under Local HTML File. The browser will parse and run the code completely offline.

4. Lite Mode & Embeds

Check the Enable Lite Mode option before submitting a URL. This will hide RawServe's user interface entirely and load the page in absolute full screen. This is perfect for generating permanent direct links or embeds.

1. Root-Relative Asset URLs

If the source HTML file references assets using absolute root paths (e.g., /style.css or /js/app.js instead of relative style.css or ./style.css), they will resolve to RawServe's host domain instead of the source repository, causing a 404 error.

2. Local CORS Restriction (file:///)

Modern browsers block JavaScript fetch() requests to local file:/// paths due to strict Same-Origin security policies. RawServe cannot fetch local files using standard input URLs. Use the Local HTML File selector to upload and read local files.

3. JavaScript SPA Routers

Single Page Applications built with complex dynamic routing (such as React Router or Vue Router utilizing HTML5 History API) may break upon manual refresh or routing, as RawServe does not configure custom dynamic server fallbacks.

4. Third-Party CORS Blockers

External APIs and fonts that do not permit cross-origin requests (CORS) might still refuse to load when imported outside of their white-listed domains.

5. SharedArrayBuffer & Cross-Origin Isolation (Godot 4/Wasm)

Modern game engines (like Godot 4 Web builds) rely on WebAssembly multithreading and require SharedArrayBuffer. Browsers strictly block these APIs unless the document is served with Cross-Origin Isolation headers (COOP and COEP). Since RawServe runs entirely on the client-side (and often loaded locally over file:/// or proxy CDNs), it cannot force these security headers natively. To load multithreaded games, you must host RawServe on a local or cloud web server (like Vercel or local Python server) configured to return COOP/COEP headers, or export your Godot project using the single-threaded template fallback.

6. Modern JS/TS Frameworks (Svelte, Next.js, Nuxt, etc.)

RawServe handles static client-side HTML, CSS, and JS. Modern development frameworks like Next.js, Nuxt, SvelteKit, or Remix rely on complex bundlers (like Vite, Webpack, or Turbopack) and Node.js server-side environments (SSR/Serverless functions). Directly serving raw uncompiled source code from these frameworks will not work because the browser cannot compile raw JSX, Svelte templates, or TypeScript on-the-fly. To run projects built with these frameworks via RawServe, you must first compile them locally or in CI, and serve their fully bundled static production export (usually located inside the exported dist or out directories).