DataTables debugger

The DataTables debugger makes it easy to provide information to assist with a support request. It can also be used to inform you when updates are available to the DataTables software you are using and run tests to find and suggest corrections for common configuration issues.

How to use the DataTables debugger

The debugger will read information about your page by loading its own Javascript. This can be done in one of two ways:

  • A Javascript snippet that is pasted directly into your browser's console.
  • As a bookmarklet

Javascript snippet

To use the debugger on your page with minimum hassle, simply copy the code below, and then paste it into the browser's debug console where and when you want to run the debugger.

var n = document.createElement('script');
n.setAttribute('language', 'JavaScript');
n.setAttribute('src', 'https://debug.datatables.net/debug.js');


If you make use of the debugger for multiple pages, you might find it useful to install it as a bookmarklet. This can be done by clicking and dragging the button to your browser's bookmark bar, or right clicking on the button an selecting "Add to bookmark. Then load the web-page with the DataTable you wish to debug and select the bookmarklet from your bookmark bar.

DataTables debug


The debugger can be used to read the configuration and data of the DataTables on your page at the time when the debugger is run. This is then uploaded to the DataTables debug server and stored in a database. The information from this upload can only be read by employees of SpryMedia and is automatically deleted after two weeks. This information uploaded will not be sold or given to third parties - it is used solely to assist with support requests. To upload data with the debugger select the "Upload" option and then confirm that you want to upload the table information. This is not required and the debugger can still be useful for checking updates and running tests on your code.

More information

The client-side script used for the debugger is open source. Contributions are very welcome! Further information about the debugger is available in the blog post introducing it.