How to export KiCad DRC JSON
Run the board DRC in KiCad or use kicad-cli pcb drc --format json --severity-all --schematic-parity -o drc.json board.kicad_pcb. Generate the baseline with the same KiCad version and CLI options when possible. Save both reports, then open them here. This page consumes the report; it does not run DRC or read the board file.
What a baseline diff means
Findings are grouped by report category, rule type, and affected item UUIDs. Within repeated groups they are paired by sorted reported position. New, resolved, changed, and persisting are report-to-report classifications, not proof that copper geometry is fixed. The comparison stops when board filenames, declared included-severity coverage, or ignored rule sets differ. Missing coverage declarations, KiCad version changes, board-file revisions, or changed DRC options still require manual review.
Excluded and ignored are different
An excluded finding still exists in the report and can carry a review comment; it is shown separately from active errors and warnings. An ignored check is a rule class that may not have been evaluated at all. A report without included_severities or ignored_checks metadata cannot establish complete coverage, even when its visible violation arrays are empty.
Fabrication and safety boundary
This is a report reader, not a design-rule checker, electrical review, or fabrication sign-off. It cannot verify board geometry, clearances, nets, stackup, manufacturer limits, rule configuration, zone refill, schematic parity unless included in the supplied report, or whether exclusions are justified. Run KiCad DRC on the exact board revision with appropriate options, review every active and excluded issue, and follow the fabricator’s requirements before release.
Frequently asked questions
Can I upload a .kicad_pcb board here?
No. Export KiCad’s JSON DRC report first. This tool does not parse or modify PCB design files.
Why is a baseline comparison blocked?
Different board filenames, severity coverage, or ignored rule sets can make disappearances look like fixes. Re-export reports with comparable settings or inspect them separately.
Does a “resolved” row prove the board is fixed?
No. It means that matching rule and item UUIDs do not appear in the current report under comparable declared coverage. A changed rule, file, design, or DRC execution can also remove a row.
Are excluded findings counted as errors?
No. They have their own count and retain their original severity in detail and CSV so the review decision remains visible.
KiCad references
KiCad documents the PCB DRC JSON export and severity options, and publishes the DRC v1 JSON schema used for the report structure. Newer KiCad versions may change report details; the page preserves unknown rule names as written.
Inspect an IBIS model · Inspect CANopen EDS/DCF · Browse electronics tools