Prerender.io alternative pricing in 2026: what renders cost and what to compare before you switch
Since Prerender.io's September 2026 pricing update, its Starter plan costs $59 a month with 30,000 renders included, up from 25,000. Renders past the included allowance are extra renders, and the notice prices them per 1,000. So when you price an alternative, compare three things at your own volume: the monthly price, how many renders it includes, and what happens when you go past that. One option is RenderSwap, a hosted prerender service. Its Pro plan is $19 a month for 30,000 fresh renders, and there are no overage bills: past the cap, your origin answers. Before you compare any plans, though, work out how many renders you actually use. The steps below show how.
What Prerender.io charges after the September 2026 update
Prerender.io's pricing notice is dated September 14, 2026. It reads: Starter moves to $59 per month with 30,000 renders included (up from 25,000), Growth to $169 per month, and Pro to $419 per month. The notice's rate card also has a column for extra renders per 1,000.
| Plan | Monthly price |
|---|---|
| Starter | $59, with 30,000 renders included |
| Growth | $169 |
| Pro | $419 |
Not every account changed on the same day. Per the notice, each account moves to the new rate on its own first billing date on or after September 15, 2026. The notice also says enterprise and custom-priced contracts are not affected by this update. Before you compare a quote against last month's invoice, check which rate that invoice used.
Work out how many renders you use before comparing
A monthly price only means something next to your volume. Prerender.io defines a render as one server-side page execution, and extra renders as the renders you use beyond your plan's included allowance. Its notice also says a cache hit serves a previously rendered page without re-executing it, and cache hits are free. Its plan guide says your monthly render volume depends on how many URLs you have and how often you want them recached. Use these steps to get a figure for your own site:
- Count your URLs. The plan guide suggests you use your sitemap or a tool like Google Search Console to find your total URL count, and it notes that more pages means more renders.
- Decide how fresh cached pages need to be. In the plan guide's words, shorter intervals mean more frequent recaching and higher render counts, and a longer interval reduces monthly renders significantly.
- Check whether you need both mobile and desktop rendering. Prerender.io renders them separately, so turning on both roughly doubles your render count there.
- Clean up broken URLs. The notice says renders of error responses are billable, so broken URLs in your sitemap quietly use up your allowance.
- Watch your cache hit rate. The notice says to aim for a cache hit rate above 70%.
Once you have a monthly figure, compare plans at that figure, not at each plan's headline. Work out what each plan would cost you at that figure once extra renders are added, and check whether a plan with spare room would let you recache more often.
Compare alternatives on what happens past the cap
The headline price tells you what a normal month costs. Also check how each plan would handle a busy month, a crawl spike or a sitemap full of broken links. Put the same questions to every service you consider, and get the answers from its own pricing page or terms:
- Is a cache hit counted as a render, or is it free?
- Is a failed render counted, and is the browser time it used counted?
- Above the cap, do you get an overage bill, a hard stop, or a fallback to your own server?
- How many domains does each plan cover, and are subdomains included?
- What do you have to change in your code or settings to switch, and how do you switch back?
Write the answers in one table next to your monthly render figure. That table is the comparison to trust, because it uses your traffic and your risk.
What a switch changes in prerender-node
If your site uses the prerender-node middleware, the service it calls is a setting. Its README says the middleware checks if the request is from a crawler by checking the user agent string. If you don't set a custom URL, it uses the service already deployed by prerender.io. You can point it elsewhere with the PRERENDER_SERVICE_URL environment variable or the prerenderServiceUrl option. Your token is set with the prerenderToken option. The README shows these forms:
$ export PRERENDER_SERVICE_URL=<new url>
app.use(require('prerender-node').set('prerenderServiceUrl', '<new url>'));
app.use(require('prerender-node').set('prerenderToken', 'YOUR_TOKEN'));Before you change anything, write down your current service URL and token. Then, if the new service doesn't work out, rolling back just means putting the old values back. After the switch, request one of your pages with a crawler user agent and with a normal browser, and check that each gets the page you expect.
RenderSwap as one option
RenderSwap is a hosted prerender service for sites that build their pages in the browser. It opens your own public pages in a browser and returns the finished HTML to search and AI crawlers. If you already send crawler requests to Prerender.io's service URL, you change two values: the service URL becomes RenderSwap's, and the token becomes a RenderSwap token. Your middleware stays. A Prerender.io token gets a 401 from RenderSwap, which is why both values change.
| What you compare | RenderSwap Pro | Prerender.io Starter |
|---|---|---|
| Monthly price | $19 | $59 |
| Renders included | 30,000 fresh renders or 30 browser hours, whichever comes first | 30,000 |
| Past the cap | Your origin answers; no overage bill | Extra renders, priced per 1,000 |
| Cache hits | Not a render | Free |
There is also a Free plan: 1 verified domain, and 500 fresh renders or 1 browser hour a month, whichever comes first. It needs no card and no email address to sign up. Pro covers 3 verified domains. You prove you control a domain with a TXT record in its DNS, and RenderSwap renders only your own pages on domains you have verified.
When a render fails, the crawler gets your origin's own page. That covers a timeout, a site that blocks the renderer, and a month past your cap. The dashboard lists the pages that fell back and the reason for each. On 4 November 2026, the unmodified prerender-node 3.8.3 middleware passed 8 of 8 swap checks against RenderSwap. They included a visitor getting the site unchanged, a crawler getting the page's client-rendered text, and a second request being a cache hit.
Know the limits before you choose it: above 30,000 renders a month is not for sale yet. So if your render figure from the steps above is higher, RenderSwap is not the right fit today. RenderSwap is not affiliated with or endorsed by Prerender.io.
Sources
- Prerender.io September 2026 pricing notice
- Prerender.io guide to choosing a plan
- prerender-node middleware setup guide
Questions
How much is Prerender.io's Starter plan in 2026?
Prerender.io's notice dated September 14, 2026 says Starter moves to $59 per month with 30,000 renders included, up from 25,000. Each account moves to the new rate on its own first billing date on or after September 15, 2026.
Do cache hits count as renders?
On Prerender.io, the notice says cache hits are free. On RenderSwap, a page already stored is served without a browser, so a cache hit is not a render.
Do I have to replace my prerender-node middleware to switch services?
prerender-node reads its service URL from PRERENDER_SERVICE_URL or the prerenderServiceUrl option, and its token from prerenderToken. To move to RenderSwap, you change the service URL and the token; the middleware stays.
What if I need more than 30,000 renders a month?
RenderSwap does not sell plans above 30,000 renders a month yet. Prerender.io's notice lists Growth at $169 per month and Pro at $419 per month. Size your volume with the steps above before you pick a plan.