Rendertron
GoogleChrome/rendertronReviewed by AI
Checked by RepoPicks Radar on
What is Rendertron?
A server from the Google Chrome team that loads a web address in an invisible Chrome, waits for the JavaScript to finish and returns the finished HTML, so search engines and other bots see the real content of a JavaScript site. It can also take screenshots. You run it yourself with Node and Chrome installed, and add a piece of middleware to your own site. The authors marked it deprecated and will not maintain it, and the repository is archived and read-only.
Rendertron is free and open source (Apache-2.0) and can replace Prerender.io.
How easy is it to install Rendertron?
C · install 1 or 2 tools · Windows
- Windows C
- macOS C
- Linux C
A C on all three, and Linux is where it is normally deployed: you install Node, have Chrome on the machine, then `npm install -g rendertron` and run `rendertron`, or clone and `npm install && npm run build && npm run start`. There is no installer and no graphical window — it is a server plus middleware you add to your own site, and the README now points to Puppeteer's own troubleshooting guide for Docker since "Rendertron no longer includes a Docker file".
Rendertron on GitHub
- Stars
- 5,948on Nov 10, 2026
- Downloads
- —all releases
- Growth
- —no gain in the last reading
Stars over time
Facts
- Runs on
- Windows, macOS, Linux
- You need to install
- Node.js, Other tools
- To build from source
- Node.js
- Disk space
- 100 MB–500 MB · estimate
- Accounts or keys
- None
- Cost
- Free · No price (Apache-2.0). If you follow the Google Cloud deployment route, Google charges for the hosting.
- License
- Apache-2.0 (Permissive)
- Can replace
- Prerender.io
- Last change on GitHub
- Oct 6, 2022
Rendertron risk signals (8)
- Attentionstale releases
Last release on 2020-11-04 (2192 days ago)
automatic check
- Attentiondeprecated by authors
README.md top section: "Rendertron is deprecated... Dynamic rendering is not a recommended approach and there are better approaches to rendering on the web. **Rendertron will not be actively maintained at this point.**" The repository is archived and the last release, 3.1.0, is from 2020-11-04.
AI review
- Attentionrenders any url by default
The endpoints are `GET /render/<url>` and `GET|POST /screenshot/<url>`, and the two options that limit them are off by default: `renderOnly` ("restrict the endpoint to only service requests for certain domains") is not set, and `restrictedUrlPattern` has "_default `null`_". An instance left open on the internet will fetch and screenshot whatever address anyone sends it.
AI review
- Attentionold unpatched dependencies
package.json pins `puppeteer: ^10.0.0`, `koa: ^2.13.1`, `typescript: 4.0.5` and `engines: { node: >=10 }`, all from 2020–2021, and the project is archived so they will not be updated. Puppeteer 10 also downloads its own old build of Chromium.
AI review
- InfoRepository archived
The repository is archived (read-only, no longer maintained)
automatic check
- Infopublic demo instance in the docs
The repository homepage and a README example use a shared hosted instance, `https://render-tron.appspot.com/render/...`. Sending your pages through someone else's server means they see every address you render, and nothing in an archived project promises it stays up.
AI review
- Infoten second render limit
README FAQ: "There is a hard limit of 10 seconds for rendering", with the `timeout` config defaulting to 10000 ms. Slow pages come back unfinished.
AI review
- Infoneeds code changes on your site
README.md: "you'll need to implement the differential serving layer. This checks the user agent to determine whether prerendering is required." Only the Express.js middleware lives in this repository; the Firebase, ASP.net and Django ones are listed as "Community maintained".
AI review
Evidence is shown in its original language.
What Radar could not check about Rendertron
- Whether it still builds and runs with current versions of Node and Chrome
- Whether the hosted render-tron.appspot.com instance still answers
- How well search engines treat pages served this way today, given Google's own advice against dynamic rendering
- Real memory and disk use with a Chrome running behind it
- Whether the community middleware projects still work