Image-Charts vs Chart-Output: An Honest Comparison for Production Pipelines
Want to see the output first? Render a chart in the playground. No account needed.
If you're building automated reports, embedding charts in emails, or running a data pipeline that outputs images, you've probably landed on Image-Charts as the incumbent option. It grew out of the Google Image Charts format, and it works.
This post compares Image-Charts and Chart-Output directly: input format, pricing, output formats, and where each tool fits best. We re-checked every Image-Charts figure against its pricing page and documentation on November 16, 2026, and corrected the ones from our June version that no longer held.
What both tools do
Both services solve the same core problem: you have data, you need a chart image, and you can't run a browser or a frontend to generate it. You call an API, you get back a PNG (or SVG or PDF), and you embed it wherever you need it — email, Slack, a PDF report, a webhook payload.
Neither requires a headless browser. Neither stores your chart data after rendering. Both have been built specifically for server-side, automated workflows.
The differences show up in how you describe a chart to the API, what you can do with the output, and what it costs at scale.
Input format: URL parameters vs Chart.js JSON
This is the main technical difference between the two services, though it's narrower than it used to be.
Image-Charts started with a URL parameter format inherited from the original Google Image Charts API. A chart is described in a query string:
https://image-charts.com/chart?cht=bvs&chs=700x200&chd=t:10,20,30&chl=Jan|Feb|MarThis works, and the compatibility with Google's deprecated format means a lot of existing code can point to Image-Charts without changes. Encoding a complex chart in that format (custom colors, multiple datasets) means building a long query string that is hard to version and debug. Image-Charts also accepts a Chart.js config in the URL, so a Chart.js chart doesn't have to be translated into the parameter format.
Chart-Output takes a Chart.js JSON configuration via POST body:
POST /v1/render
{
"type": "bar",
"data": {
"labels": ["Jan", "Feb", "Mar"],
"datasets": [{ "label": "Revenue", "data": [10, 20, 30] }]
},
"options": { "plugins": { "legend": { "display": true } } }
}Chart.js is the most widely used open-source charting library in the world. If you've ever built a dashboard, you've probably already written a Chart.js config. Reusing that config in an API call is the point of Chart-Output. The config is a plain JSON object in the request body: easy to generate in code, version control and validate, with no URL length to manage.
The honest summary: both services can take a Chart.js config. Chart-Output sends it as a POST body, and Image-Charts puts it in the URL.
Output formats
| Format | Image-Charts | Chart-Output |
|---|---|---|
| PNG | ✓ | ✓ |
| SVG | Not in its documentation | ✓ |
| WebP | Listed on its pricing page | ✓ |
| Not in its documentation | Pro and above | |
| Animated GIF | ✓ | ✗ |
| High resolution | Enterprise plan | Every plan, up to its pixel limit (1,200 px on Free, 3,000 px on Pro and Agency) |
Image-Charts documents PNG and GIF output. Animated GIF is genuinely useful for email marketing, and Chart-Output doesn't offer it. Chart-Output has PDF output on Pro and above, which matters for report generation pipelines.
Brand kits and white-labeling
Image-Charts offers watermark removal and a custom subdomain on the Business plan ($99/month, or $89/month billed yearly). That's the extent of the branding it lists: you can remove its watermark and serve images from your own domain.
Chart-Output has brand kits: you define a color palette, typography, and logo once, reference it by ID on any API call, and every chart renders consistently with your brand applied automatically. This is meaningfully different from just removing a watermark. If you're building a SaaS product where end users receive charts, or an agency running reports for multiple clients, brand kits let you manage multiple visual identities from a single integration.
Logo support is included — pass a logo URL in your brand kit and it renders into each chart at a defined position.
For teams embedding charts in customer-facing products, this is the sharpest differentiator between the two services.
Pipeline features: sync vs async
Image-Charts' documentation describes synchronous requests: you make a request, you get an image back, and we found no async jobs or webhooks in it. For simple workflows this is fine. For batch pipelines that generate hundreds or thousands of charts, you manage the concurrency yourself.
Chart-Output supports both:
- Synchronous rendering for inline calls where you need the image immediately
- Async batch rendering with webhook delivery for pipelines — submit a job, receive a signed payload to your webhook URL when rendering completes. Idempotency keys prevent duplicate renders on retries.
If you're running a reporting pipeline that generates end-of-month PDFs for 500 customers, async batch with webhook delivery is a meaningful operational difference.
AI generation
Chart-Output has an AI rendering endpoint: send a natural language description and raw data, and the endpoint constructs the chart spec and returns a rendered image. This is useful for pipelines where the chart type isn't known in advance — user-driven analytics, dynamic reporting, or AI-assisted dashboards.
We found no AI generation endpoint in Image-Charts' documentation.
Pricing
| Plan | Image-Charts | Chart-Output |
|---|---|---|
| Free | Free forever, unlimited API calls, small watermark | 1,000 renders/month, small watermark |
| Entry paid | Business: $99/mo, or $89/mo billed yearly. Unlimited API calls, no watermark, Zapier and Make integration | Pro: $19/mo, 25,000 renders/month, no watermark, PDF |
| Next | Enterprise: $249/mo, or $224/mo billed yearly. High-resolution and compound charts | Agency: $79/mo, 150,000 renders/month |
| Higher volume | An on-premise appliance plan | Custom |
A few things worth noting:
Image-Charts charges a flat fee per tier with unlimited API calls. That's predictable. It also means the Zapier and Make integration starts at $99 a month, or $89 a month if you pay for the year.
Chart-Output charges by render volume. Pro is $19 a month for 25,000 renders with no watermark, and Agency is $79 a month for 150,000 renders. Above that, Custom is arranged directly.
For teams with moderate render volumes, Chart-Output's entry price is lower. If you render far more than 150,000 charts a month, Image-Charts' flat-rate model may come out cheaper, and its Free tier has no render cap if you accept the watermark.
Where each tool fits
Image-Charts is a better fit if:
- You have existing code built against the Google Image Charts URL format and want a drop-in replacement
- You need animated GIF charts for email campaigns
- You prefer flat-rate pricing regardless of render volume
- You need an on-premise option
Chart-Output is a better fit if:
- You're already using Chart.js and want to send your configs as a JSON body, not in a URL
- You need brand kits for multi-client or white-labeled output
- You're building async pipelines and need webhook delivery
- You want AI-assisted chart generation for dynamic or conversational workflows
- You're on a tighter budget at entry-level volumes
Summary
Image-Charts is a proven, stable service. If you're migrating from Google Image Charts or you've already built against their format, it does the job.
Chart-Output is built for teams who want a JSON request body, brand kits applied by id, and async jobs with signed webhooks, at a lower entry price.
Both offer a free tier. The fastest way to decide is to run the same chart spec through both and compare the output against your requirements.