How to Format SQL and Replace Parameter Placeholders

Every backend engineer has been there. You're chasing down a slow query or a bug in production, so you open the application logs and copy out the SQL — and it's a single 300-character line with no indentation, no line breaks, and a trail of ? marks where the real values should be. Before you can even run it against the database, you have to make sense of it and fill in those placeholders by hand. This guide shows you how to do both in seconds.

Why readable SQL matters

SQL is declarative, which means the order you write clauses in isn't the order the database evaluates them in. A query with several joins, subqueries, and a GROUP BY is hard enough to reason about when it's laid out cleanly — squashed onto one line, it's nearly impossible. Formatting adds the structure your brain needs to parse it:

• Spot the logic fast — each clause (WHERE, JOIN, GROUP BY, HAVING) sits on its own line, so you can jump straight to the condition you care about.
• See relationships at a glance — joins and their ON conditions line up, making it obvious which table connects to which.
• Review and refactor safely — consistent formatting means code reviews focus on logic, not on arguing about style.

How to format SQL step by step

Formatting takes one paste into our free SQL Formatter:

• 1.Paste your SQL into the input box — it formats automatically as you type or paste.
• 2.Tune the options to taste: uppercase keywords, indent size (2, 4, or 8 spaces, or tabs), and whether to append a trailing semicolon.
• 3.Click Format SQL to re-beautify, or Minify SQL to collapse it back onto one line for logging or embedding.
• 4.Click Copy Result to grab the clean output.

The formatter understands the common dialects — MySQL, PostgreSQL, SQLite, SQL Server, Oracle — and handles SELECT, INSERT, UPDATE, and DELETE, including joins, unions, subqueries, window functions, and CASE expressions.

Filling in parameter placeholders

Here's the part that turns a confusing chore into a one-click job. When SQL comes out of an ORM, a prepared statement, or a monitoring dashboard, the values are almost never inline — they're replaced by placeholder markers. The marker depends on your database:

To turn one of these back into a query you can actually run, the SQL Formatter has a Parameter Fill panel. Pick the placeholder format, click Auto-detect Parameters, and the tool lists every placeholder it found. Type a value into each field and format again — the values are substituted in.

The substitution is smart about types. A number like 42 is inserted as-is; text is wrapped in single quotes with any embedded quotes escaped; and keywords like NULL, TRUE, or CURRENT_DATE are kept verbatim. So you don't have to remember whether that ? was a string, a number, or a boolean — the tool handles it.

A real example: from log line to runnable query

Here's a query you might pull straight out of a slow-query log:

After formatting and filling in the four ? placeholders with paid, 2025-01-01, 100, and 20, it becomes:

SELECT
    o.id,
    o.customer_id,
    c.name,
    SUM(oi.quantity * oi.price) AS total
FROM
    orders o
JOIN
    customers c
    ON c.id = o.customer_id
JOIN
    order_items oi
    ON oi.order_id = o.id
WHERE
    o.status = 'paid'
    AND o.created_at >= '2025-01-01'
GROUP BY
    o.id,
    o.customer_id,
    c.name
HAVING
    SUM(oi.quantity * oi.price) > 100
ORDER BY
    total DESC
LIMIT 20;

The difference is night and day: you can see the join path, the filters, and the aggregation in one glance — and the query is ready to paste into your database client and execute.

Why it runs entirely in your browser

SQL is rarely harmless. A production query often encodes table names, business logic, and the exact filters your app uses — information you wouldn't want sitting on someone else's server. That's why the formatter processes everything locally: your query is never uploaded, never logged, and never leaves your device. Paste a query with real customer data or proprietary schema, and it stays private.

Frequently asked questions

Working with a lot of nested data too? Learn how to pull specific values out of it with How to Query JSON with JSONPath, or clean up raw JSON with How to Format and Validate JSON.