Alternative
A QuickChart alternative without the 10,000-renders/month cap
QuickChart's Professional plan is $40/month and lists “Rate limit enforced: 10,000 images/month”. UrlChart's paid plan has no hard monthly cap — a 100,000 unique-render soft ceiling and a conversation, never a cut-off.
We are not affiliated with QuickChart. Prices are their published list prices, checked 2026-11-17 (UTC). Their free community tier and open-source renderer are genuinely useful; this page is about the two specific constraints our pilot found.
The cap
| Plan | List price | Monthly images | What happens at the limit |
|---|---|---|---|
| QuickChart Professional (vendor page) | $40/mo | 10,000 images/month, rate limit enforced | Throttled by the vendor's rate limit |
| QuickChart Enterprise | Contact sales | No rate limits (vendor page) | Sales negotiation decides |
| UrlChart | $29/mo $290/yr |
100,000 unique renders/month soft ceiling; 10,000/day trigger | Throttled to 30 req/min + we contact you; production traffic is not blocked |
For a dashboard or an emailed report, 10,000 renders can disappear in a week. The metering rule matters as much as the number: on UrlChart, identical URLs are served from the edge cache and cached images are never counted. A chart embedded in a page seen by 100,000 people is one render, not 100,000.
The error behaviour we measured
In a 41-URL compatibility pilot run on 2026-11-17, we sent real-world Google-legal chart URLs to QuickChart's /gchart endpoint and recorded the raw responses. 11 of the 41 URLs (27%) were hard errors, returned either as a short text body (“Sorry, this chart configuration is not supported right now”) or as an error image. The failures clustered in exactly the families people migrate for: multi-axis, radar with fills, scatter, and marker-heavy charts.
The pilot also records silent degradation — HTTP 200 with a parameter quietly ignored — because that is the harder failure to notice. Our position is not that QuickChart is bad. It is that a migration needs a report, not a guess: the Drop-in Tester shows what our renderer does with the same URL, and our renderer's own behaviour is to render an approximation and say so.
If you are already on QuickChart
- Legacy
/gchartURLs: keep the parameters, swap host and path tourlchart.com/chart(or/gchart— both resolve to the same renderer and share a cache entry). Addkey=if you want the unwatermarked tier. - Chart.js JSON URLs (
?c=…): those are not legacy parameter URLs. UrlChart accepts Chart.js JSON viaPOST /chart, with the body as the configuration. The tester will tell you when it sees a non-legacy URL. - Short URLs and plugins: not implemented. Keep QuickChart if you depend on them; UrlChart is focused on the legacy parameter surface.
Usage limits are explained once, on Unlimited charts — subject to Fair Use, including what a unique render is and the exact behaviour past the soft ceiling.
Try a URL before migrating. Paste it into the Drop-in Tester: you get the original image (loaded by your browser), our render, and the parameter report. Nothing is stored.
Common questions
Is 10,000/month really enforced?
That is what QuickChart's own pricing page says for the Professional plan (“Rate limit enforced: 10,000 images/month”), checked 2026-11-17. We have not measured their enforcement behaviour; check with them for current terms.
Do you support Chart.js configuration JSON?
Yes, via POST /chart with a Chart.js configuration body. It is not accepted as a GET query parameter, and POST /gchart is rejected — that mirrors the legacy endpoint's contract.
What if my chart type is not supported at all?
QR codes, maps, Venn diagrams, formulas, funnels and meters are not implemented. They return an approximate bar chart or a text card and are marked degraded, rather than returning an error image. If you need the exact original visual, keep the tool that has it.