SQL Query Explainer (plain English)

Explains a SELECT, INSERT, UPDATE, DELETE or CREATE TABLE statement in plain English: tables and joins, filters, grouping, ordering and limits, in logical order, with warnings for common pitfalls.

Use the tool

Why this tool exists

Reading someone else's query, or your own from six months ago, is slow when it has four joins, a HAVING clause and a nested condition. A plain-English walk-through helps you check that the query does what you think. This tool describes the steps in the order the database logically evaluates them: where the rows come from, how tables are joined, what filters apply, how results are grouped and sorted, and what is returned. It also warns about common problems such as SELECT *, a LIKE with a leading wildcard, functions applied to columns, large OFFSET values, and UPDATE or DELETE without WHERE. It uses rules, not an AI model, so CTEs, UNION and window frames are not supported. Your SQL stays in your browser.

How to use it

  1. Paste a single SQL statement into the input box.
  2. Run the explanation to read the steps and the warnings.
  3. Compare it with your intent and fix any warning that applies.

Frequently asked questions

Does it use AI?

No. It is a rule-based parser that follows the structure of the statement. That makes it fast and private, but limited to the patterns it knows.

What is not supported?

CTEs (WITH), UNION, window function frames and other advanced syntax. Statements using them may be explained incompletely or not at all.

What warnings does it give?

SELECT *, LIKE patterns starting with a wildcard, functions on columns in WHERE, big OFFSET values and UPDATE or DELETE without a WHERE clause.

Can it tell me if the query is fast?

No. It never sees your data or indexes. For performance, check the plan with EXPLAIN and use the PostgreSQL plan visualiser or the index advisor on this site.