Free tools · PC & console

See the changes.
Keep control.

Compare configuration versions before you update your server. Find what was added, removed or changed.

Files stay in this browser tab. No uploads to Forge, no shared drafts, no automatic changes to your server. Start with the example to see how it works.
01 · Before

Original configuration

02 · After

Edited configuration

Choose two files of the same kind, or try the example.

Designed for your server files.

Supports named entries in types.xml, events.xml, cfgeventspawns.xml and cfgspawnabletypes.xml. Files must have matching roots and unique entry names. Custom class names are welcome; this is a structural comparison, not a live compatibility test.

JSON comparison uses property paths. Arrays are compared as complete values. XML comments and formatting whitespace are ignored; child-element order is significant. Changes to comments are not reported. PC and console owners can compare their own map-appropriate files.

Preview the VIP merge workflow.

Example · M4A1 conflict

Original baseline

<nominal>5</nominal>

Current server

<nominal>10</nominal>

Proposed update

<nominal>15</nominal>

Both versions changed the same entry. In the member workspace you inspect all three versions, select the entry to keep, and review the full plan before downloading.

CHOICE REQUIRED

Need to combine several configuration files?

The VIP workspace compares a shared original with current server files and proposed changes, then asks you to resolve conflicting entries before export. Included in the existing $140 USD / two-month package.

Explore VIP merging →