---
schema_version: "1"
id: e8ef7c2ce225d99ae7c9f49c6f78a9a2a0b425168fd55639f98c66de9b29bd4f
title: Visualforce Charting Limitations and Considerations
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/salesforce-pages-developers-guide/guides/pages/charting/pages-charting-limitations.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-pages-developers-guide/guide/pages-charting-limitations.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 2d01fcbcea8285777a661e67fc1c56978dfcc63819804f802395e4dca7178e0e
products:
  - Visualforce Developer Guide
  - Platform Developer Content
---

# Visualforce Charting Limitations and Considerations

This section lists considerations and known limitations for Visualforce Charting.

-   Visualforce charts only render in browsers which support scalable vector graphics (SVG). For more information, see [W3C SVG Working Group](http://www.w3.org/Graphics/SVG/).
-   Visualforce charting uses JavaScript to draw the charts. Visualforce charts won’t display in pages rendered as PDFs.
-   Email clients don’t usually support JavaScript execution in messages. Don’t use Visualforce charting in email messages or email templates.
-   Visualforce charting sends errors and messages to the JavaScript console. Keep a JavaScript debugging tool, such as Chrome DevTools or Safari Web Inspector, active during development.
-   Dynamic (Apex-generated) charting components aren’t supported at this time.