Upload two files to see the diff
Or pick a sample from the sidebar to get started.
Example comparisons
- XLSXExcel BOMTwo workbook revisions compared in the table itself - changed cells highlighted where they changed, added and removed rows marked.
- PDFPDF drawingDrawings, P&IDs and specs page by page, side by side, with alignment correction for a sheet that shifted between revisions.
- PPTXPowerPoint design reviewDesign-review decks compared slide by slide, so the changes are found before the meeting instead of during it.
- VSDXVisio P&IDVisio diagrams rendered and compared as diagrams - the P&ID case Visio itself has no usable compare for.
- PNGBlock diagram (PNG)Pixel-accurate comparison for exported diagrams, plots and scans - the differences eyes do not catch.
- STEPSTEP 3D model3D models rendered in the browser: see what changed between two revisions of a part without a CAD seat.
- STLSTL mesh (AI-lightened bracket)Triangle meshes from generative design, code-CAD and slicers, with the changed geometry lit up in a heat map.
- DOCXWord specA redline through the document - insertions and deletions marked, tracked-changes style, without opening Word.
- JSONJSON configConfigs and machine exports compared as structured JSON, with the raw text a click away.
- SVGSVG diagramVector diagrams compared as drawings, not as the XML a layout engine rewrote wholesale.
- DXFDXF drawing2D CAD drawings rendered and compared with no AutoCAD on the machine.
- L5XRockwell PLC projectRockwell Studio 5000 exports read as projects - tags, routines, ladder logic - with the changed rungs highlighted.
- REQIFReqIF requirementsRequirement baselines from DOORS, Polarion or Jama compared requirement by requirement - reworded text as a redline, moved chapters and changed links called out.
- NCCNC toolpath (G-code)CNC programs drawn as toolpaths per tool, with the moved hole, the new feed and the added finishing pass called out.
- BDFNASTRAN wing ribNASTRAN FEA decks drawn as a 3D mesh - changed elements painted on it, moved nodes marked, property and material changes listed.
- DEXPIDEXPI P&ID (amine contactor)P&IDs as data, not a picture: the DEXPI/Proteus XML from AVEVA, SmartPlant and Comos drawn as a diagram and compared tag by tag.
- RAWPSS/E power-flow casePSS/E power-flow cases drawn as a one-line diagram by voltage level - renamed buses, re-dispatched generators and tap changes called out.
- SCDIEC 61850 substationIEC 61850 substation configuration read as a substation - IEDs, GOOSE and Sampled Value publications - so a re-pointed subscription is found before it trips a line.
- GTLGerber PCB copperGerber layers drawn as the fab reads them from the RS-274X, with the added and removed copper and the aperture changes listed.
- KICAD_SCHKiCad schematicKiCad schematics drawn from the file's own symbols and wires, with added, removed and changed symbols, wires and labels marked on the sheet.
- KICAD_PCBKiCad PCB layoutKiCad boards drawn per layer - footprints moved, rotated or re-netted, changed tracks, vias and zones, and per-net length deltas.
- SLXSimulink modelSimulink models drawn in Simulink's own layout - blocks added, moved or re-parameterised and re-routed signals marked, system by system.
- MOModelica modelModelica models drawn from their diagram annotations, with changed components, parameters, connects and equations listed class by class.
- ORKOpenRocket designOpenRocket designs drawn from the component tree - re-dimensioned parts, motor configurations and simulation results compared.
- ASCLTspice schematicLTspice schematics drawn from the built-in symbol library, with re-valued parts shown as 10k → 4.7k and changed nets and wires marked.
- IFCIFC building modelIFC models from Revit, Tekla or Plant 3D read as a building - spatial tree, storey plan, property sets - and compared element by element.
- PLCOPENPLCopen controls programIEC 61131-3 programs in PLCopen XML from Codesys, TwinCAT, EcoStruxure and B&R - ladder, function blocks, SFC and Structured Text - compared rung by rung.
How it works
- 1Pick a sample from the sidebar, or skip straight to your own files.
- 2Drop the before and after versions into the two slots - up to 25.0 MB each, two files of the same type.
- 3Read the comparison. Share turns it into a link when someone else needs to see it.
FAQ
Is it free?
Yes - no account, no trial clock. The diff playground is the free corner of Kord, version control for engineering document sets; a comparison you can run in ten seconds explains the product better than a brochure.
What happens to my files?
They are kept only as long as it takes to render the comparison. Most formats are read in your browser; Word and PowerPoint are converted to a preview server-side in memory, and a file too large for a request body travels through a short-lived upload that is swept automatically. Nothing is stored, and there is no account to attach a history to. The longer answer is on the security page.
What is the size limit?
25.0 MB per file. Larger Office files are routed through the short-lived upload behind the scenes, so they behave the same as small ones.
Can I share a comparison?
Yes. Share mints a link that renders the same diff for whoever opens it - no account on their end either.
Can an AI agent or a script create a comparison link?
Yes, with no sign-in. POST the two files to https://work.withkord.com/api/diff/share as multipart fields named before and after; the JSON response carries a url that opens for anyone, for 7 days by default (ttlDays sets it, up to a month). The two files are kept only until the link expires. The full contract, including the upload step for files over about 4 MB, is in the OpenAPI document at https://work.withkord.com/openapi.json.
Can I compare more than two files?
That is Kord itself: version control on whole document sets, this same visual diff between any two revisions of every file, review sessions with sign-off, and an audit trail tied to what was issued. Try Kord from the header, or read the format guides on the marketing site.
Format-by-format guides - what the comparison shows, how the alternatives stack up - live at withkord.com/compare, alongside Git for documents, the longer answer to why version control for engineering files is harder than it looks.