Prerender.io pricing update, September 2026

TL;DR 

Prerender.io pricing for the Starter, Growth, and Pro plans updates on September 15, 2026: 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 new rate applies on your first billing cycle on or after September 15, so nothing changes mid-cycle and there is nothing for you to do. Enterprise and custom-priced contracts are not affected by this update.

What is changing

The table below shows the current rate and the new rate for each self-serve plan. A render is one server-side page execution, and extra renders are the renders you use beyond your plan's included allowance.

On Starter for instance, the included allowance grows by 5,000 renders alongside the price. That keeps the effective rate on your included renders close to flat, moving from roughly $1.96 to roughly $1.97 per 1,000, and gives you more room before you use any extra renders.

When the new pricing applies to your account

The change is not a single cutover date for everyone. Each account moves to the new rate on its own first billing date on or after September 15, 2026.

If your renewal falls on September 20, your September invoice reflects the new pricing. If it falls on October 3, your September invoice is unchanged and the new pricing starts in October. You can check your renewal date in your Prerender.io dashboard under Settings > Billing.

 What this is going towards 

The pricing update follows value that has already shipped, plus work that is underway.

• AI Insights, included on every plan. AI Insights shows you which AI crawlers reach your site, which pages they see, and what is blocking them. Around two-thirds of active Prerender.io accounts already receive AI-crawler traffic, and AI Insights is how you see whether GPTBot, ClaudeBot, and other AI crawlers are reading your content or skipping it. It is delivered in your dashboard and as a recurring digest. 72% of all sites we’ve looked at have had at least one AI crawler blocked, without even realizing it. AI Insights catches this at the source. 

• Search Performance. Prerender.io is working on Search Performance, which would connect your rendering data to Google Search Console so you can see how your rendered pages perform in search results without leaving your account. It is not available yet, and we will announce it when it ships.

• Tighter security. We're currently in the process of our SOC 2 Type II and ISO 27001 certifications. These are world-leading, premier security frameworks to guarantee and ensure continuous protection for our customers. This a lengthy process that requires resources, time, and investment.  

Behind the scenes, we’re also working hard on our detailed roadmap with new features, more integrations, streamlined support, and a cohesive, unified platform shift. 

Why Prerender.io pricing is changing

Rendering at scale is compute-heavy. Every cache miss runs a real headless browser session on real hardware, and compute costs have risen sharply across the industry over the past year. If you run your own infrastructure, you have likely seen the same movement in your own bills.

Prerender.io is absorbing the majority of that increase rather than passing it through in full. This update covers the remainder and funds the roadmap above.

The way people find content is also changing quickly, with AI platforms now sitting alongside search engines. Prerender.io is being built so your site stays readable across AI and search platforms as that shift continues.

What you need to do

Nothing. The new pricing applies automatically on your next billing cycle after September 15, 2026, and your integration, your cache, and your rendering behavior are unaffected. Your website visitors see no change.

If you want to review your plan, you have three options:

• Check your usage first. Open your Prerender.io dashboard to see how many renders you actually use each month. Most Starter accounts use well under the included allowance, so the larger 30,000-render allowance is headroom rather than a cost.
• Talk it through. Email support@prerender.io if you want help finding the plan that fits your usage. Our Customer Support team will reply personally.
• Manage your subscription. You can change or cancel your plan at any time in Settings > Billing.
  
  

How to keep your render usage down

If extra renders are a concern, the lever that matters most is your cache hit rate. A cache hit serves a previously rendered page without re-executing it, and cache hits are free.

• Aim for a cache hit rate above 70%. Below 50% means your pages are being re-rendered more often than they need to be.
• Check whether you need both mobile and desktop rendering. Prerender.io renders them separately, so enabling both roughly doubles your render count. 
• Review your recache interval. Re-rendering pages more frequently than your content actually changes spends renders for no benefit.
• Check whether you need both mobile and desktop rendering. Prerender.io renders them separately, so enabling both roughly doubles your render count.
• Watch for error pages. Renders of 3xx, 4xx, and 5xx responses are billable, so broken URLs in your sitemap quietly consume your allowance.

If you are on an Enterprise or custom plan

Enterprise and custom-priced contracts are not part of this update. Your pricing is set by your contract, and any change to it is handled directly with your account team. If you are unsure which applies to you, check Settings > Billing in your dashboard or email support@prerender.io.

Related articles

• Understanding your render usage and billing explains what counts as a billable render and where to see your usage.
• How to improve your cache hit rate covers the settings that reduce re-renders.
• How Prerender.io works walks through the request flow from crawler request to cached HTML.
• Get started with Nexus, your AI integration assistant shows how to check and fix your integration from inside your dashboard.