1 item
Capture XML API responses on any page and compare two of them on comparexml.com. Compare XML captures XML API responses as you browse and lets you diff any two of them side by side on comparexml.com — no copy-pasting, no manual file juggling. DEBUG API CHANGES IN SECONDS When a frontend bug appears, the first question is always "what changed in the response?". Instead of digging through DevTools network panels and pasting payloads into a diff tool, just: 1. Press Start in the extension popup 2. Reproduce the two scenarios (or browse two pages / two environments) 3. Pick a Base and a Contrast from the captured list 4. Click Compare — a visual diff opens instantly KEY FEATURES • Automatic capture — hooks into fetch/XHR and records every XML response, including direct navigation to .xml URLs • You control when — Start/Pause toggle, nothing is recorded while paused • Works across tabs — captures from all open tabs merge into one list, perfect for comparing staging vs. production • Full privacy control — capturing is off by default; one click clears everything • Toolbar badge — see the captured count at a glance • Powered by comparexml.com — structural XML diff with syntax highlighting and collapsible tree view WHO IS IT FOR • Frontend developers debugging API contract changes • QA engineers verifying backend deployments • Anyone working with SOAP, RSS/Atom feeds, sitemaps, or other XML payloads PRIVACY Captured data never leaves your browser. It is stored locally in session storage, is cleared when you close the browser, and can be wiped at any time with the Clear button. No analytics, no tracking, no accounts.
Aug 25, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.