A visual diff built for architectural drawings

Why architectural drawings need their own treatment

Architectural drawings are a particularly hostile case for generic document-comparison tools. Three reasons:

• They're almost entirely graphical. Text-based diff tools see lines, walls, hatching and annotations as "an image" and skip them. The actual content of the drawing is invisible to them.
• The information density is high. A single A1 plan can contain thousands of distinct elements — every door swing, window opening, dimension, grid line, callout, hatch region, room tag. The eye gives up after about 30 minutes of careful comparison.
• Tiny visual changes carry real meaning. A 50 mm change to a partition position. A door swung the other way. A hatch that changed from concrete to insulation. These are real design decisions that read as nearly identical when scrolling quickly.

PDFverifier renders both PDFs at high resolution and compares the actual pixels. Every difference, regardless of size or content type, is detected and presented for review.

Works with output from any major BIM/CAD tool

Source format doesn't matter — PDFverifier compares the rendered PDF, not the underlying file. Architects typically export from:

Drawing types and what gets compared

The full architectural drawing set typically includes several distinct drawing types. PDFverifier handles each:

A few practical tips for architects

• Use ZIP for full packages. Drop the whole sheet set in a ZIP rather than uploading sheet by sheet. PDFverifier matches sheets by filename (so keep your sheet naming consistent between revisions).
• Run before coordination meetings. A revision change list takes 5 minutes to generate and saves an hour of "wait, was that changed?" in the meeting.
• Use it for QA before issuing. Run the comparison on your own revisions before sending them out — you'll catch missed coordination items and forgotten revision clouds.
• Annotate with comments. Each detected change can carry a comment. Useful for "ignore — drafting cleanup" vs "design intent change — confirm with engineer".
• Don't trust raster-rendered viewports for small text. Revit viewports can rasterise small annotations differently between exports. If you see weird false positives, increase the export DPI on both revisions.

What it doesn't do

Being honest about the limits:

• Doesn't read your model. PDFverifier works on PDFs, not Revit/ArchiCAD files. It compares what was actually drawn, not what's in the underlying model.
• Doesn't auto-generate revision clouds. The output is a marked-up PDF showing changes — not a redline-cloud overlay on your model.
• Doesn't know intent. It tells you what changed, not why. The "why" still requires you to talk to the team that made the change.
• Doesn't replace a coordination check. It compares the architectural set against itself between revisions. It doesn't check architectural against structural or MEP — for that, run a comparison per discipline.