SQL Formatter for Data Analysts — Clean Queries for Reports

As a data analyst, you write SQL all day in tools that were not designed for writing SQL. Looker has a SQL Runner with a basic editor. Tableau has Custom SQL with no formatter at all. Mode and Hex have decent editors but no consistent formatting button. Snowflake's worksheet has the Cmd+Shift+F shortcut that breaks on long queries. By the end of the day you have written 40 queries and formatted exactly zero of them.

Our formatter handles the analyst workflow specifically. Paste any query from any BI tool, pick the dialect, get clean output you can share with stakeholders, save in a Confluence runbook, or paste into a Slack message without it looking broken. No upload, no install, no Looker license needed.

Why Data Analysts Need a Separate SQL Formatter

BI tools are designed for visualization, not for writing SQL. The query editors built into them are minimal:

• Looker SQL Runner — basic textarea, no auto-format, no syntax-aware indentation.
• Tableau Custom SQL — no formatting at all. The query box is pure text input.
• Mode Analytics — has a decent editor but no built-in format button.
• Hex — Python-friendly notebook editor, SQL formatting is rudimentary.
• Sigma — visual query builder primarily, SQL view has no formatter.
• Power BI — DirectQuery and Native Query editors have no SQL formatter.
• Metabase — query editor is basic, no format button.
• Redash — query editor lacks formatting features.

The result: analysts write SQL in tools without formatters, and the queries stay messy until someone has to share them. Then it is too late — the analyst is in a meeting and has to read out a wall of text.

What Analysts Need That a Generic Formatter Has to Handle

Analyst SQL has some patterns that less-analyst-focused formatters mishandle:

Long SELECT lists with 20-50 columns. Marketing analytics queries pull dozens of attributes. The formatter needs to put each column on its own line so they can be reviewed and reordered.

Heavy use of CTEs. Modern analyst SQL relies on CTEs for readability — base data, transformations, aggregations, final select. The formatter needs to space CTEs visually.

Window functions for cohorts. COHORT analysis uses ROW_NUMBER, LAG, LEAD, and SUM OVER constructs. The formatter needs to lay these out clearly.

Date and time gymnastics. DATE_TRUNC, DATE_PART, EXTRACT, INTERVAL — analyst queries use a lot of date functions. Formatting needs to keep these readable.

Pivot/unpivot patterns. CASE WHEN aggregates for manual pivoting are common. The formatter should keep CASE expressions readable.

JOIN soup. Star schema queries can have 5-10 LEFT JOINs. Each JOIN needs to be on its own line with the ON clause clearly visible.

How to Format a Dashboard Query in Your Browser

1. Copy the query from your BI tool — Looker SQL Runner, Tableau Custom SQL editor, Mode editor, Hex SQL cell, anywhere.
2. Paste into our formatter input.
3. Pick the dialect — match your data warehouse: Snowflake (use BigQuery), BigQuery, PostgreSQL (Redshift), Standard (Databricks), Transact-SQL (Synapse).
4. Set indent to 2 spaces — most modern data team style guides use 2 spaces, matching dbt conventions.
5. Toggle uppercase keywords on — standard for analyst SQL.
6. Click Format — output appears with clean indentation.
7. Copy back into your BI tool, dashboard, or documentation.

For queries that drive production dashboards, save the formatted version to your team's git repo so the next analyst can read it.

Sell Custom Apparel — We Handle Printing & Free Shipping

Real Data Analyst Use Cases for SQL Formatting

Share a query in Slack. A stakeholder asks "how did you calculate active users last week?" You share the query. Without formatting, the wall of text gets ignored. Formatted, it gets read.

Document a dashboard. Every dashboard should have a Confluence page explaining what it shows and how. Paste the formatted SQL so the next analyst can understand the methodology.

Code review a colleague's query. When reviewing a teammate's PR for a dbt model or a Looker view, format their SQL first to spot bugs visually.

Translate a stakeholder request to SQL. Product asks "how many users converted in the last 7 days?" Write the query, format it, attach it to the response so they can verify the logic.

Save a query to a runbook. Incident response often includes "run this query to check current state." Format the query so the on-call analyst can read it at 3am.

Export to Tableau Custom SQL. Tableau's Custom SQL editor mangles formatting. Format the query externally first, then paste into Tableau exactly the way you want it.

Why Formatting Matters More for Analysts Than for Engineers

Backend engineers write SQL inside larger codebases. The SQL is one part of a Python script or a Java service, and most readers will be other engineers who can read SQL natively.

Analysts write SQL that ends up in front of business stakeholders. Product managers read it (sort of). Marketing reads it (less so). Executives glance at it and decide whether to trust the number. For these audiences, formatting is the difference between a number being trusted and being challenged.

A formatted query says "I am precise about my work." A wall of unformatted SQL says "I do not care enough to make this readable." Even if the underlying query is identical, the perception is different.

For analysts, formatting is professional polish. For engineers, it is a nice-to-have.

Other Browser Tools Data Analysts Bookmark

Analysts deal with more than just SQL. These browser tools handle adjacent tasks:

JSON formatter — for cleaning up API responses before pulling them into your warehouse. JSON Formatter.

CSV to JSON converter — for converting small CSV exports to JSON for stakeholder reports. CSV to JSON.

SQL diff checker — for comparing two versions of a query when refactoring a metric definition. SQL Query Diff.

Cron expression generator — for setting up scheduled queries in BigQuery, Snowflake tasks, or Airflow DAGs. Cron Generator.

Frequently Asked Questions

Does this work with Looker SQL Runner queries?

Yes. Copy the query out of Looker SQL Runner, paste into our formatter, format, paste back. The formatter handles the dialect of whatever data warehouse Looker is connected to (BigQuery, Snowflake, Redshift, Postgres).

Will it format Tableau Custom SQL queries?

Yes. Copy the query from the Tableau Custom SQL editor, paste into our formatter, format, paste back. Tableau accepts the formatted version exactly as pasted.

Can I format queries with LookML or dbt jinja templating?

The SQL portions format cleanly. Templating directives like {% if %} or {{ ref(table) }} pass through as text — they are not interpreted. For full dbt-aware formatting, install SQLFluff with the dbt plugin and run it in your project.

Does the formatter work for Snowflake-specific syntax like QUALIFY?

Yes. Pick the BigQuery dialect, which handles most Snowflake-specific syntax including QUALIFY, FLATTEN, COPY INTO, and time travel queries.

Can I use this on a corporate analyst laptop where I cannot install software?

Yes. The formatter is a website. It runs in any browser with no install. Works on locked-down corporate Windows, Mac, and Linux machines.