CSV SafePreview · E2 local prototype

Validate a CSV before it becomes SQL.

Inspect row shape and inferred types, quote identifiers safely, preview conservative PostgreSQL or SQLite SQL, and export only a clean parse.

Private by design.
CSV text is read in this browser only. Nothing is uploaded, saved, tracked, or sent to an account.

1. Load a CSV

2. Choose preview settings

Structural errors and a contract FAIL block SQL generation. A contract PASS or WARN keeps export available. All table and column identifiers are double-quoted; text literals escape single quotes.

QA results

No CSV analyzed yet
Analyze a CSV to see transport preflight details.

    Inferred schema

    Analyze a CSV to see conservative type inference.

    Optional destination contract preflight

    Paste a small local contract to compare expected columns, types, nullability, uniqueness, and allowed values. Use the header column,type,required,nullable,unique,allowed_values; separate allowed values with |. PASS and WARN permit export; FAIL visibly blocks the SQL preview and download until the contract or CSV is corrected.

    Analyze a CSV, then optionally check it against a destination contract.

    SQL preview

    Import readiness report

    Turn the analysis into a local Markdown handoff with the findings, inferred schema, transport notes, and a review checklist. It never includes a network destination.

    Future Pro hypothesis: a bounded Import Readiness Pack could add destination-column mapping, normalization decisions, larger local batches, and a human-reviewed plan. Pricing and payment are not active.

    Worked example: a WARN is a review signal

    Example: A CSV can parse cleanly and still receive a WARN for padded whitespace, an empty value treated as NULL, or a value that falls back to text. The SQL preview remains available, but the destination may receive a different value or type than you assumed. Inspect the cited row or column, decide whether the source or destination contract should change, then run the check again before importing.

    A WARN does not certify an import. It explains a bounded risk while leaving the preview available; a FAIL blocks the preview until the reported contract or structural issue is addressed.

    A complete pre-import workflow

    1. Diagnose

    Find row-shape, transport, header, whitespace, NULL, and mixed-type hazards before SQL is generated.

    2. Preview

    Review conservative PostgreSQL or SQLite types and quoted identifiers without silently repairing the source.

    3. Contract check

    Compare a local destination contract with the inferred source shape and see explicit mismatches.

    4. Handoff

    Download SQL and a readable report so a teammate can review assumptions before an import.

    This is a local diagnostic aid, not a database connection, migration service, schema guarantee, or production-import approval.