Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Highcharts JS, the JavaScript charting framework
JavaScript HTML PHP Java Other
Branch: master
Failed to load latest commit information.
errors Changed description for error 23 (related to #3920).
exporting-server Export: Phantomjs exporting charts in a oversized PDF
gfx Finalized radial/circular gradients for VML
grunt-tasks Created node script for copying files to shim repos and committing.
js Fixed #4536, unable to zoom in closely on first category when minRang…
lib Utils: Worked around errors from canvg.
samples Fixed #4536, unable to zoom in closely on first category when minRang…
studies Changed some files when adding data module to the docs
test add %k in dateFormat
tools Final changes before release
utils Utils: Improved phantomjs runner
.gitignore Ignore logfiles
ant 3D: Changes and cleaning
bower-info.js Added bower file and info
bower.json Added bower file and info Removed unused heading Cleaned up after release
build.xml Added the experimental boost module to build.
changelog-highcharts.htm --- Highcharts 4.1.8 / Highstock 2.1.8 / Highmaps 1.1.8 official rele…
changelog-highmaps.htm --- Highcharts 4.1.8 / Highstock 2.1.8 / Highmaps 1.1.8 official rele…
changelog-highstock.htm --- Highcharts 4.1.8 / Highstock 2.1.8 / Highmaps 1.1.8 official rele…
copy-release.js Cleaned up after release
generate-changelog.js Utils: Changelog script
gruntfile.js Additions to the previous
invalidations.txt Preparations for highcharts-3d module in parts.
package.json Added repository information to package.json fix hightcharts support link in

Highcharts JS

Highcharts JS is a JavaScript charting library based on SVG and VML rendering.

Reporting issues

We use GitHub Issues as our official bug tracker. We strive to keep this a clean, maintainable and searchable record of our open and closed bugs, therefore we kindly ask you to obey some rules before reporting an issue:

  1. Make sure the report is accompanied by a reproducible demo. The ideal demo is created by forking our standard jsFiddle, adding your own code and stripping it down to an absolute minimum needed to demonstrate the bug.
  2. Always add information on what browser it applies to, and other information needed for us to debug.
  3. It may be that the bug is already fixed. Try your chart with our latest work from before reporting.
  4. For feature requests, tech support and general discussion, don't use GitHub Issues. See for the appropriate channels.

Apply a fix

When an issue is resolved, we commit a fix and mark the issue closed. This doesn't mean that a new release is available with the fix applied, but that it is fixed in the development code and will be added to the next stable release. Stable versions are typically released every 1-3 months. To try out the fix immediately, you can run or from any website, but do not use these URLs in production.

If the fix is critical for your project, we recommend that you apply the fix to the latest stable release of Highcharts or Highstock instead of running the latest file found on GitHub, where other untested changes are also present. Most issues are resolved in single patches that don't conflict with other changes. If you're not into Git and don't want to install and learn that procedure, here's how to apply it quickly with help of online tools:

  • Locate your issue on GitHub, for example #2510.
  • Most issues are closed directly from a commit. Go to that commit, for example d5e176.
  • Now add .patch to the URL to view the patch file.
  • The patch file will show diffs from all files changed. Here it's important to be aware that highcharts.src.js, highstock.src.js and highcharts-more.src.js are concatenated from parts files. Instead of applying the patches from part files, you only need those from the concatenated files.
  • If you need to patch highcharts.src.js, copy the diff for that file. Start selecting including the line diff --git a/js/highcharts.src.js b/js/highcharts.src.js and select all text until the next diff statement for the next file.
  • Now the patch is on your clipboard, open another tab at
  • Under "Original file", click "By URL" and enter or another source file from the latest stable release, see
  • Under "Second file or patch file" click "Direct input" and paste the diff from your clipboard.
  • Click the "Patch" button, and if everything is okay you should now have a patched file.
  • The next (optional) step is to compile the source code in order to reduce file size. Copy the result from the patched file.
  • Go to the Closure Compiler web app.
  • Paste the patched file contents to the left and click "Compile".
Something went wrong with that request. Please try again.