What happens when you reach your Prerender render limit
Hitting your render limit doesn't break your site — here's what it means and what to do about it.
TL;DR
Reaching your render limit doesn't stop AI crawlers and search engines from accessing your existing cached pages — they keep serving normally. New requests beyond the limit continue to be rendered, but each one counts as an extra render and adds to your bill. You can resolve this by upgrading to a plan with more included renders, or by reducing usage to stay within your current plan.
What reaching the render limit means
When your account reaches its render limit, existing cached pages continue serving to AI crawlers and search engines without interruption. Prerender doesn't stop rendering new requests — it keeps working, but each additional render beyond your plan's included amount is charged as an extra render.
ℹ️ Reaching your render limit doesn't prevent AI crawlers from accessing your existing cached pages. Only new renders beyond the limit incur extra charges.
What drives render usage
Render usage typically increases for two reasons.
On-demand renders. When a crawler requests a page that isn't in your cache yet, Prerender renders it immediately. The more uncached pages your site has — from new content, new URLs, or a recent cache clear — the more on-demand renders accumulate.
Automatic recaching. Prerender recaches pages periodically based on your cache expiration settings. The shorter your cache expiry, the more frequently pages are re-rendered and the faster your render usage climbs.
For a full breakdown of how renders are counted and what affects your limit, see how renders are calculated.
Your two options
Upgrade your plan
If your site consistently needs more renders than your current plan includes, upgrading gives you full coverage without extra charges on top. See the Prerender pricing page for options, or read how to find the best plan for your site to compare plans before upgrading.
Reduce your render usage
If you'd rather stay on your current plan, targeted adjustments can significantly cut unnecessary renders — for example, excluding pages that don't need to be cached, extending cache expiry intervals, or filtering out requests that shouldn't be reaching Prerender.
See how to reduce the number of pages Prerender caches for specific steps.
💬 Still need help?
If you're not sure what's driving your render usage, our support team can help you investigate and find the right path forward.
→ Contact us at support@prerender.io