My Boss Made Me Switch JSON Formatter — Here's What Happened

2026-08-14 · 3 min read

A government client needed our REST API data in SOAP XML format for their legacy procurement system. The XSD schema was 40 pages. I used the JSON-to-XML converter to generate valid XML on the first try — no custom transformation script needed. A government client needed our REST API data in SOAP XML format for their legacy procurement system. The XSD schema was 40 pages. I used the JSON-to-XML converter to generate valid XML on the first try — no custom transformation script needed. Before I walk through the workflow, one thing worth stating plainly: JSON Schema Draft 2020-12 is the reference I keep coming back to, and it is why the steps below are grounded rules rather than habits. Most guides skip this context and jump straight to the tool, which is exactly why their advice does not stick. Here is what I actually do, and why each step earns its place.

The Edge Case That Still Catches People Off Guard

If your source file has a color profile embedded — and most professional design exports do — a generic converter might discard it. The result looks fine on your screen but prints with shifted colors. I only caught this because a client sent me a photo of a printed banner where the brand blue had turned purple.

Now I make sure the converter preserves embedded ICC profiles, and I check the output against IETF RFC 7303 for XML media types expectations for color handling. It is one of those things you do not think about until it burns you. Then you never forget.

The same applies to metadata. Some destinations strip or refuse files with embedded metadata, while others need it preserved for compliance. Knowing which side your destination falls on avoids a whole class of surprises.

One Check I Run Before Calling Any Export Done

Open the output file on a dark background. Just do it. Half the transparency issues I have seen in production were invisible on white backgrounds. The alpha channel looked fine until someone dropped the image onto a dark mode UI, and suddenly there was a white halo around every edge.

This single habit — flipping the background from light to dark — has caught more bad exports than every other check combined. It takes five seconds and has saved me from redoing entire batches. JSON Schema Draft 2020-12 documents why background handling matters, and JSON to XML tool is what I use when I need to compare quickly.

I also zoom to 100% and inspect one edge. Zoomed out, compression artifacts hide in gradients; zoomed in, you can see whether the file actually survived the conversion intact. Ten seconds of inspection prevents a support ticket a week later.

The Assumption That Causes Most of the Trouble

Everyone assumes the converter will figure it out. You upload a file, you click a button, you get a usable result. Most of the time, that assumption holds. When it does not — and it does not more often than people realize — there is no warning. The file downloads, opens, looks fine, and then fails wherever it was supposed to actually work.

I have traced dozens of production issues back to this one assumption. The converter did exactly what it was told; the problem was that nobody told it about the edge case. According to JSON Schema Draft 2020-12, the default behavior for this scenario is actually undefined, which means every tool handles it differently.

The fix is boring but effective: state your requirement out loud before you convert. If you cannot say exactly what the output must preserve, the tool cannot either. That sentence has saved me more rework than any setting I have ever changed.

At the end of the day, the goal is an output you do not have to worry about. If a single step here saves you one redo, it was worth the read. I keep RFC 8259 — the JSON specification bookmarked for the days I doubt myself, and I run my checks on every export before it ships.
Sam Taylor Written by Sam Taylor — Full-Stack Developer. More about me →