API response comparison
Compare JSON responses from v1 and v2 endpoints to confirm added fields, removed fields, and value changes during integration or regression testing.
A: JSON A
B: JSON B
JSON Diff and Compare Tool
Compare two JSON documents side by side, inspect added, removed, and changed fields, and export summaries, Markdown reports, or JSON Patch. Everything runs locally in your browser.
Tekan Ctrl/Cmd+D untuk menandai alat ini
Best-fit scenarios
Configuration drift review
Compare development, staging, and production JSON config files while using ignore-order rules to reduce irrelevant noise.
Data migration validation
Check old and new JSON structures after migration work so renamed fields, default values, and split objects are easy to verify.
Log and snapshot comparison
Compare two requests, logs, or state snapshots to understand exactly what changed before and after an issue appeared.
Two JSON file diff
Import or paste two JSON files and inspect structural and field-level differences for configs, exports, fixtures, or API samples.
Cara membandingkan file JSON secara online – panduan langkah demi langkah
1Langkah 1 – Tempel atau impor kedua file JSON2Langkah 2 – Atur opsi perbandingan3Langkah 3 – Tinjau visualisasi diff4Langkah 4 – Ekspor hasil
Gunakan alat pembanding JSON online ini untuk melihat dua objek JSON berdampingan, menyorot perbedaan, dan mengekspor patch atau laporan untuk kontrol versi dan pengujian API.
Understand version drift before acting on it
The compare tool helps answer what changed, not just whether the text looks different
In most workflows, you care about whether fields were added, removed, or changed in meaning, not whether two files differ by whitespace or order. That is why a structural JSON compare is more useful than plain text diff.
JSON A (older version)
1
{
2
"id": 1,
3
"name": "Maeve",
4
"status": "active",
5
"roles": ["admin", "editor"]
6
}
JSON B (newer version)
1
{
2
"id": 1,
3
"name": "Maeve Winters",
4
"status": "active",
5
"roles": ["admin", "editor"],
6
7
}
If you only need the high-level answer first, read the summary. If you need exact field-level context, stay in the diff view.
3 compare examples that reflect real work
These examples mirror the most common JSON diff workflows in development, QA, and operations: API upgrades, environment config review, and data migration verification.
API Versioning
Compare API response v1 and v2 to confirm added fields
This is ideal when frontend and backend teams need to verify exactly what changed between response versions.
Response v1
1
{
2
"user": {
3
"id": 42,
4
"name": "Maeve"
5
},
6
"status": "active"
7
}
Response v2
1
{
2
"user": {
3
"id": 42,
4
"name": "Maeve"
5
},
6
"status": "active",
7
"profile": {
8
9
}
10
}
This kind of diff is especially useful when you need to verify added fields before updating tests or frontend models.
Environment Config
Remove ordering noise so the real config differences stand out
When object keys or array members are semantically unordered, selective ignore rules can reduce a lot of useless diff noise.
Staging
1
{
2
"features": ["coupon", "betaCheckout"],
3
"retry": 2,
4
"timeout": 5000
5
}
Production
1
{
2
"features": ["betaCheckout", "coupon"],
3
"retry": 3,
4
"timeout": 5000
5
}
With ignore order enabled, the important change becomes obvious: retry changed, while the feature list did not meaningfully drift.
Migration Review
Check data migration output and export a Patch for automation
This works well when old structures are being split, renamed, or normalized into a new shape.
Before migration
1
{
2
"fullName": "Maeve Winters",
3
"active": true
4
}
After migration
1
{
2
"firstName": "Maeve",
3
"lastName": "Winters",
4
"status": "active"
5
}
If the migration pipeline needs repeatable change application, exporting both the Markdown report and JSON Patch is often worthwhile.
- 01
Tutorial Step
Langkah 1 – Tempel atau impor kedua file JSON
Before you look at the diff, be clear about what each side represents: old versus new, staging versus production, previous response versus current response. That mental model makes the later change review much easier.
- Tempel JSON pertama ke editor kiri (JSON A) dan JSON kedua ke editor kanan (JSON B).
- Atau gunakan Impor untuk memuat JSON dari file, URL, atau clipboard pada masing-masing sisi.
- Gunakan respons API nyata, file konfigurasi, atau ekspor data untuk membandingkan perubahan yang relevan.
- Try to compare payloads from the same business scope or time window so you do not mix unrelated changes into one review.
- Check the imported names or source labels before reviewing the diff so you do not accidentally reverse the sides.
- 02
Tutorial Step
Langkah 2 – Atur opsi perbandingan
Ignore whitespace, case, and order are useful only when they match the meaning of your data. The fastest approach is to choose them intentionally instead of enabling every option by default.
- Aktifkan Abaikan spasi untuk fokus pada struktur, bukan format.
- Aktifkan Abaikan huruf besar/kecil untuk membandingkan kunci dan nilai string tanpa membedakan kapital.
- Aktifkan Abaikan urutan saat urutan elemen tidak seharusnya dihitung sebagai perubahan.
- When any ignore rule is enabled, the page switches to a normalized preview so the highlights match the actual comparison logic.
- If you are unsure whether order matters, review the raw diff first and turn on ignore order only after you confirm the noise pattern.
- 03
Tutorial Step
Langkah 3 – Tinjau visualisasi diff
A useful comparison is more than colored highlights. The best signal usually comes from combining three things: the field-level diff, the change counts in the status area, and the high-level summary you can copy or export.
- Tampilan berdampingan menyorot penambahan (hijau), penghapusan (merah), dan perubahan (kuning).
- Gunakan status bar untuk melihat total perubahan dan ringkasan per kategori.
- Beralih antara mode Sisi dan Inline sesuai ukuran layar atau preferensi.
- Copy Summary is useful when you need to explain the result quickly in a ticket, chat, or review thread.
- If the diff suddenly looks much larger than expected, confirm that the two payloads actually come from the same source scope before digging deeper.
- 04
Tutorial Step
Langkah 4 – Ekspor hasil
This page does not just show differences. It can produce three useful outputs depending on what happens next: summary text for communication, Markdown reports for documentation, and JSON Patch for automation.
- Salin ringkasan untuk membagikan perubahan dengan cepat di chat, tiket, atau dokumentasi.
- Ekspor laporan Markdown dengan perubahan dan statistik yang lebih detail.
- Ekspor JSON Patch (RFC 6902) untuk menerapkan perubahan secara terprogram.
- For config comparisons, keep the report with version identifiers so rollback and audit are easier later.
- If one of the payloads still needs field-by-field review, move it into the table editor after the comparison step.
A more reliable compare workflow
1
Validate both payloads first so broken JSON does not pollute the diff.
2
Review the raw comparison once before enabling ignore rules so you understand what noise is present.
3
Use the diff highlights, counts, and summary together to judge the scale and type of change.
4
Use summary text for communication, Markdown reports for records, and JSON Patch for automation.
5
If one side still needs field-level inspection or editing, continue into the formatter or table editor after comparison.
The compare page is best used to answer not whether two files look different, but where the JSON structure and meaning actually changed.
Tips cepat untuk membandingkan JSON
Validasi kedua JSON terlebih dahulu agar kesalahan sintaks tidak menyembunyikan perbedaan yang sebenarnya.
Saat membandingkan respons API, pertimbangkan untuk mengaktifkan Abaikan urutan agar tidak bising karena array yang tertukar urutannya.
Gunakan ekspor JSON Patch saat Anda membutuhkan diff yang dapat diproses mesin untuk menyinkronkan lingkungan.
If the diff is hard to read, format both payloads first, then compare again.
Alat terkait untuk perbandingan & diff JSON
Gabungkan alat-alat ini dengan perbandingan JSON untuk alur validasi, pemformatan, dan pembuatan kode.
Pertanyaan yang Sering Diajukan
Bagaimana cara kerja perbandingan JSON?
Alat ini melakukan diff struktural untuk mendeteksi penambahan, penghapusan, dan perubahan pada objek maupun array bertingkat.
Apakah data JSON saya diunggah?
Tidak. Semua proses berjalan secara lokal di browser Anda dan tidak pernah diunggah ke server kami.
Opsi perbandingan apa saja yang tersedia?
Anda dapat mengabaikan spasi, mengabaikan huruf besar/kecil, dan mengabaikan urutan untuk fokus pada perubahan struktur yang penting.
Bisakah saya mengabaikan spasi?
Bisa. Opsi ini menormalkan spasi di dalam nilai string. Spasi di luar string sudah diabaikan saat parsing JSON.
Bisakah saya mengabaikan huruf besar/kecil?
Bisa. Saat diaktifkan, kunci dan nilai string dibandingkan tanpa membedakan huruf besar/kecil untuk mengurangi perbedaan yang tidak penting.
Bisakah saya mengabaikan urutan?
Bisa. Opsi ini memperlakukan kunci objek dan elemen array sebagai tidak bergantung urutan, cocok untuk daftar yang urutannya tidak bermakna.
Mengapa editor kadang menjadi hanya-baca?
Saat opsi pengabaian diaktifkan, tampilan beralih ke pratinjau yang dinormalisasi agar penyorotan sesuai dengan aturan tersebut. Matikan opsi untuk kembali mengedit JSON mentah.
Apa itu JSON Patch (RFC 6902)?
JSON Patch adalah standar daftar operasi (add, remove, replace, dll.) untuk mengubah satu dokumen JSON menjadi dokumen lainnya.
Bagaimana JSON Patch yang diekspor dibuat?
Kami menghitung set operasi yang andal dari A → B berdasarkan jalur JSON Pointer. Untuk array, kami bisa menggunakan penggantian yang konservatif agar tidak terjadi pergeseran indeks.
Bagaimana cara mengekspor atau membagikan hasil?
Gunakan Salin ringkasan untuk menyalin gambaran singkat, Ekspor laporan untuk mengunduh laporan Markdown, atau Ekspor JSON Patch untuk menerapkan perubahan secara terprogram.