Skip to main content

Confirm

Are you sure?

Node.js · Code recipe

Get the rendered HTML of a JavaScript page in Node.js

Fetch the HTML a browser ends up with, JavaScript and all, in Node.js 18+ with the built-in fetch. Every program on this page runs as it stands — each one was run against a stub of the API before it was published.

By · Last updated: September 2026

TL;DR

To get the HTML of a JavaScript-rendered page in Node.js, POST its URL to https://urlpipe.dev/html with sync set to true. The body is the DOM after the page's scripts ran in real Chrome, serialized as HTML — what a visitor's browser holds, not what the server first sent — read with await res.text(), for 1 credit.

Free plan, no credit card. 1,000 credits a month.

One POST to /html loads the page in real Chrome, lets its JavaScript run, and serializes the DOM it ended up with. For a single-page app that is the difference between an empty <div id="root"> and the content; the rendered vs raw HTML guide shows how far apart the two get.

The body is the HTML as text, read with await res.text(). The program saves it and reports its size in bytes — compare that with curl -s https://example.com | wc -c and you see how much of the page only exists after the scripts ran.

Setup

Before you start

Nothing to install: fetch is global from Node 18. The files end in .mjs so Node reads them as ES modules and top-level await works without a wrapper function.

Terminal
node --version   # v18 or later
export URLPIPE_API_KEY="your_api_key"

The request

Save the rendered HTML and report its size

sync: true keeps the request open until the result is ready. fetch resolves on any status, 4xx and 5xx included, so check res.ok yourself. Buffer.byteLength counts bytes; html.length would count UTF-16 code units and come out smaller on any page with non-ASCII text.

rendered_html.mjs
import { writeFile } from "node:fs/promises";

const res = await fetch("https://urlpipe.dev/html", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.URLPIPE_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ url: "https://example.com", sync: true }),
  // fetch has no timeout of its own; a sync call can take up to 60 s.
  signal: AbortSignal.timeout(90_000),
});
if (!res.ok) throw new Error(`URLpipe answered ${res.status}: ${await res.text()}`);

const html = await res.text();
await writeFile("page.html", html);
console.log(`Saved page.html (${Buffer.byteLength(html)} bytes)`);

Run it: node rendered_html.mjs

Async

The async variant: a token, a webhook and a poll

Leave out sync and the answer is a token, straight away. setTimeout from node:timers/promises is the awaitable sleep, so the polling loop reads top to bottom.

rendered_html_async.mjs
import { setTimeout as sleep } from "node:timers/promises";
import { writeFile } from "node:fs/promises";

const API = "https://urlpipe.dev";
const headers = {
  Authorization: `Bearer ${process.env.URLPIPE_API_KEY}`,
  "Content-Type": "application/json",
};

// No sync: the request is accepted at once and the work carries on without you.
const accepted = await fetch(`${API}/html`, {
  method: "POST",
  headers,
  body: JSON.stringify({
    url: "https://example.com",
    report_to: "https://your-app.com/webhooks/urlpipe",
    labels: { customer: "acme" },
  }),
});
if (!accepted.ok) throw new Error(`URLpipe answered ${accepted.status}: ${await accepted.text()}`);
const { token } = await accepted.json();
console.log(`Accepted ${token}`);

// The result is POSTed to report_to when it is ready. Polling by token is the
// other way to collect it: no endpoint needed, and a backup for the webhook.
let res;
for (let attempt = 0; attempt < 60; attempt++) {
  res = await fetch(`${API}/result/${token}`, { headers });
  if (res.status !== 202) break; // 202 means still processing
  await sleep(2000);
}
if (res.status === 202) throw new Error("Still processing after two minutes; try the token again later.");
if (res.status === 422) throw new Error(`The analysis failed: ${(await res.json()).error}`);
if (res.status === 410) throw new Error("The result is past the 30-day window; send the request again.");
if (!res.ok) throw new Error(`URLpipe answered ${res.status}: ${await res.text()}`);

const html = await res.text();
await writeFile("page.html", html);
console.log(`Saved page.html (${Buffer.byteLength(html)} bytes)`);

Run it: node rendered_html_async.mjs

Errors

Handle errors and retries

Read the status before the body: a 401 answers in plain text, so res.json() would throw. .catch(() => ({})) turns any body that is not JSON into an empty object, and the status still says what happened.

rendered_html_errors.mjs
import { setTimeout as sleep } from "node:timers/promises";
import { writeFile } from "node:fs/promises";

class URLpipeError extends Error {}

// POST a sync request and return the response, or throw URLpipeError.
async function urlpipe(path, payload, attempts = 5) {
  for (let attempt = 0; attempt < attempts; attempt++) {
    const res = await fetch(`https://urlpipe.dev${path}`, {
      method: "POST",
      headers: {
        Authorization: `Bearer ${process.env.URLPIPE_API_KEY}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({ ...payload, sync: true }),
      signal: AbortSignal.timeout(90_000),
    });
    if (res.ok) return res;
    if (res.status === 401) {
      throw new URLpipeError("401: the API key is missing or wrong. Check URLPIPE_API_KEY.");
    }

    const body = await res.json().catch(() => ({}));
    const code = body.error ?? "";
    const detail = body.message ? `${code}: ${body.message}` : code;

    if (res.status === 429 && code === "rate_limited") {
      // Sending too fast: Retry-After says how long the window has left.
      await sleep(Number(res.headers.get("Retry-After") ?? 1) * 1000);
    } else if (res.status === 429 && code === "concurrency_limit") {
      // Every parallel slot on your plan is busy with your own requests.
      await sleep(2 ** attempt * 1000);
    } else if (res.status === 504) {
      // Still running on our side; the token collects it from GET /result/:token.
      throw new URLpipeError(`504 processing_timeout: collect it later with token ${body.token}`);
    } else {
      // 403 email_unverified, 422 (a bad parameter, or a page that would not load),
      // 429 quota_exceeded: sending the same request again gets the same answer.
      throw new URLpipeError(`${res.status}: ${detail}`);
    }
  }
  throw new URLpipeError(`429: still refused after ${attempts} attempts`);
}

let res;
try {
  res = await urlpipe("/html", { url: "https://example.com" });
} catch (error) {
  console.error(`URLpipe: ${error.message}`);
  process.exit(1);
}

const html = await res.text();
await writeFile("page.html", html);
console.log(`Saved page.html (${Buffer.byteLength(html)} bytes)`);

Run it: node rendered_html_errors.mjs

Details

What to know about /html

  • The HTML is serialized from the live DOM, so it is well-formed but not byte-identical to any file on the server.
  • Pages over 10 MB of HTML are refused with The page is too big to be processed.
  • page_options.wait_for_selector waits for an element that loads late; delay waits a fixed time on top.
  • It is the whole document, scripts and styles included, not a cleaned-up version of it. For clean text, use Markdown instead.

Other languages

Get the rendered HTML of a JavaScript page in another language

More Node.js: every Node.js recipe

FAQ

Frequently asked questions

How is this different from fetching the URL myself?
A plain GET returns what the server sent before any JavaScript ran. /html returns the DOM after the page's scripts ran in real Chrome — the HTML a visitor's browser actually holds.
Can I wait for content that loads late?
Yes: page_options.wait_for_selector waits up to 10 seconds for an element to appear, and delay adds a fixed wait. If the element never appears the request is a 422 and costs nothing.
Does URLpipe follow robots.txt?
Yes, by default, for every project. You can turn it off per project, and then you are responsible for having the right to fetch those pages.
Do I need an SDK to call URLpipe from Node.js?
No package at all: Node 18 and later ship fetch, and the API is one POST per job.

Get a key and run it.

Free plan, no card. Paste your key into URLPIPE_API_KEY and every program on this page runs as it is.