Data Analysis Expressions (DAX) is a formula language introduced by Microsoft in Power Pivot and Analysis Services Tabular to define calculations and queries.

DAX Formatter is a free tool that transform your raw DAX formulas into clean, beautiful and readable code.
The syntax rules used improves the readability of the expressions, if you want learn more read the article: Rules for DAX Code Formatting.


You can format any DAX query and expression in the form:


You can call the service via standard HTTP GET and POST requests. Learn more »


DAX Formatter is not working as expected?
Please fill out the form as completely as possible.

Note: the current formula will be automatically attached to the request.

Advanced DAX Workshop

Support Us

If you use DAX Formatter for your posts, please embed our badge:

DAX Formatter by SQLBI DAX Formatter by SQLBI
<a href=""><img src="" alt="DAX Formatter by SQLBI"></a>
<a href=""><img src="" alt="DAX Formatter by SQLBI"></a>

Latest Changes

December 6, 2014:

Automatic removal of special character

When a formula was pasted from OneNote or Power Point, a few non standard characters were included (such as 0x0b and 0xa0). These characters are now replaced with spaces in the input before formatting, so the formula is correctly parsed and displayed.

November 29, 2014:

Support implicit conversion of table expression in scalar values

Certain table expressions that are converted in scalar values were not previously supported. An internal refactoring of the grammar supports now this type of conversion. As a side effect, certain syntax errors are no longer recognized by DAX Formatter, but this could be considered a benefit, because DAX Formatter now correctly format a certain number of invalid DAX syntaxes (that will generate errors once executed, anyway).

October 26, 2014:

Fixed parsing of floating point numbers

Floating point number starting or ending with “.” are now correctly recognized

August 16, 2014:

Added support to query parameters

The DAX query can have parameters with the prefix @

June 30, 2014:

Fixed issue with RELATED within EARLIER/EARLIEST

Using RELATED within EARLIER or EARLIEST was not recognized as a valid syntax.