I will convert json jsonl and XML files with validation
About this Gig
I will convert one authorised, nonsensitive file with deterministic validation.
Supported modes:
- JSON array of objects to JSONL
- JSONL objects to a JSON array
- regular-record XML to JSON
- flat-record JSON to regular-record XML
Each package covers one file within both byte and record/node limits. For JSON to XML, supply valid root and record element
names.
You receive a ZIP with the converted file, conversion-manifest.json, delivery-report.json and README.txt, plus source/output
hashes and exact record/node accounting.
This is exact conversion only. I do not infer or repair schemas, clean or enrich data, merge files, write custom code, connect
databases/APIs or interpret arbitrary XML. Archives, encrypted files, mixed-content XML, sensitive/high-risk data and
unsupported structures are refused.
One correction-only revision covers a delivery that differs from the confirmed mode/specification. A new file, mode, names or
scope needs a new order.
Working copies are purged after packaging. Delivery files remain locally for no more than 24 hours for relay; Fiverr controls
its own retention.
Convert from:
Other
Convert to:
Other
FAQ
What JSON and JSONL structures are supported?
JSON must be a top-level array of objects. JSONL must contain one valid object on each non-empty line. JSON-to-XML additionally requires flat scalar records plus valid root and record element names. Nested or ambiguous structures are unsupported.
What XML is supported?
Only strict regular-record XML with one repeated record element and consistent leaf-field structure is accepted. Mixed content, arbitrary nesting, external entities, unsafe constructs and ambiguous structures fail closed.
How are package limits measured?
Each package covers one source file and is limited by both source bytes and input records or XML element nodes. Reaching either limit exhausts the package. The production ceiling is 10 MiB and 50,000 records/nodes.
What happens if my file is unsupported?
The file is refused rather than repaired, guessed or partly converted. No converted output is delivered. A safe refusal report may explain the stable reason without exposing file content.
What does the revision cover?
One correction-only revision covers a delivery that differs from the confirmed mode and specification. A new file, mode, XML names, cleanup request or expanded scope is a new order.
How is my file handled?
Only authorised nonsensitive files are accepted. Local working copies are purged after packaging. The delivery ZIP is retained locally for no more than 24 hours for relay, while Fiverr controls its own platform copy and retention.
