Converter from JSON to YML
Free JSON to YML converter online: upload JSON, get a product YML feed and prepare data for catalog delivery to channels that need a YML structure with categories, currencies and offers.
Converter JSON → YML
Upload JSON and get YML online. Simple files work immediately, while advanced structure changes, value transformations, export filters and scheduled automation can be configured in your account after signup.
Need transformations, not just format conversion?
Sign up when you need to change values in cells, resize and convert images, or filter exports to include only selected items.
What is a JSON to YML converter
A JSON to YML converter takes data from a JSON file or API response and builds a product YML feed. This is useful when the source works in JSON but the next system needs data for catalog delivery to channels that need a YML structure with categories, currencies and offers. In a simple case, JSON keys become columns, cells or output nodes, and the products array becomes product rows. In production workflows, the output schema matters: which fields are exported, how nested objects are handled, what happens to image arrays, how columns are named and which records are excluded by filters.
When you need a converter
When data is already in JSON, but the next step needs a table, Excel file, feed or another structured format for import.
What the converter does
It reads JSON, selects repeated records, turns keys into output fields and helps save the structure for repeat exports.
Why setup matters
The same JSON can be exported in different ways: flat table, multiple sheets, feed or filtered file with renamed fields.
JSON to YML example
YML is an XML-like product feed. A JSON catalog must be assembled into shop, currencies, categories and offers, so production YML export is configured in a profile after signup.
Before
source JSON{
"products": [
{
"sku": "SKU-001",
"name": "iPhone 15",
"price": 999,
"stock": 12,
"category": "Smartphones",
"images": ["front.jpg", "back.jpg"]
},
{
"sku": "SKU-002",
"name": "Samsung S24",
"price": 899,
"stock": 8,
"category": "Smartphones",
"images": ["s24.jpg"]
}
]
}After
YML structure<?xml version="1.0" encoding="UTF-8"?>
<yml_catalog date="2026-05-25 12:00">
<shop>
<offers>
<offer id="SKU-001" available="true">
<name>iPhone 15</name>
<price>999</price>
<categoryId>Smartphones</categoryId>
<picture>front.jpg</picture>
<picture>back.jpg</picture>
</offer>
</offers>
</shop>
</yml_catalog>A profile can configure offer id, available, currencyId, categoryId, images, prices, filters and required feed fields.
After signup and profile setup
YML structure<?xml version="1.0" encoding="UTF-8"?>
<yml_catalog date="2026-05-25 12:00">
<shop>
<name>Demo shop</name>
<currencies><currency id="USD" rate="1"/></currencies>
<categories><category id="1">Smartphones</category></categories>
<offers>
<offer id="SKU-001" available="true">
<name>iPhone 15</name>
<price>999</price>
<currencyId>USD</currencyId>
<categoryId>1</categoryId>
<picture>front.jpg</picture>
<picture>back.jpg</picture>
</offer>
</offers>
</shop>
</yml_catalog>When you need a JSON to YML converter
This conversion is usually part of regular catalog, price-list, stock and supplier-data preparation, not just a one-off file.
Supplier catalogs
JSON from a supplier API can be mapped to the structure needed for catalog, prices, stock and images.
Price lists
Prices, currencies, discounts and stock can be prepared for later import or delivery.
CMS and ERP
Data can be adapted to the format expected by a website, CMS, ERP, PIM or internal system.
Marketplaces and channels
Catalog data can be prepared for channel requirements where required fields and stable ids matter.
Analytics and checks
Managers can review assortment, prices and stock in a clear table or feed structure.
Recurring exports
A profile can run repeatedly and deliver the result by email, FTP/SFTP, webhook or another channel.
Common JSON to YML conversion mistakes
Most problems come from JSON structure: nesting, arrays, value types and fields that do not match the receiver.
Repeated node not selected
If JSON contains products, offers or items, define which array becomes output rows.
Lost nesting
YML needs required nodes, currency, categories and valid offer ids; simply moving JSON keys is usually not enough
Different fields per product
If some records miss a field, decide whether to keep it empty, fill a default value or exclude the record.
Value types not normalized
Prices, dates, true/false and empty values should be normalized before export.
Unneeded records exported
Filters help export only active products, required categories, stock records or selected suppliers.
No result check
Before scheduling, check preview, required fields, encoding and several test records.
JSON to YML online or manual conversion
A one-time check and a production export need different approaches. Compare the options before setting up the process.
| Method | Pros | Cons |
|---|---|---|
| Manual code | Maximum flexibility for unique schemas. | Requires a developer, tests and maintenance. |
| Local script | Fast for a repeat technical task. | Harder to manage files, logs, permissions, schedules and delivery. |
| Eofferix | Preview, profiles, rules, files up to 2 GB and scheduled runs. | Complex structures need a saved profile. |
Limits, safety and production workflows
Eofferix helps check JSON structure and prepare output without changing the source file. For recurring catalogs, large files and exact rules, use a saved profile.
Up to 5 MB without signup
Good for quick checks of simple JSON files.
Up to 2 GB after signup
Large catalogs and recurring files are processed with saved rules.
Source stays unchanged
Eofferix creates a separate result.
Structure control
If keys or nesting change, update only affected rules.
Value transformations
Cleanup, normalization, prices, filters and fields.
Result delivery
Email, FTP/SFTP, webhook and other channels.
Other JSON conversions
Eofferix can also help with other formats for catalogs, price lists and supplier exports.
JSON → CSV
Build a table from JSON objects or arrays.
JSON → XLS
For Excel-compatible files and older table imports.
JSON → XLSX
For modern Excel exports, reports and multiple sheets.
JSON → XML
When the receiving system needs XML tags and nesting.
XML → JSON
Reverse conversion for APIs and web apps.
How to convert JSON to YML
Upload a JSON file
Drop the file on the page or choose it from your computer. Quick checks without signup support files up to 5 MB.
Check the output structure
Eofferix reads JSON, detects repeated records and shows a result preview.
Download the file or save a profile
Download the result immediately or sign up to configure structure, larger files and scheduled runs.
What the JSON to YML converter supports
What the JSON to YML converter supports
Small JSON files can be checked directly on the page, while production rules are saved in a profile.
Nested objects and arrays
Eofferix helps turn nested data into a clear output structure: columns, sheets, nodes or feed fields.
Field mapping
Rename fields, choose order, skip unnecessary values and prepare the file for the receiving system.
Export filters
Export only the products, categories, stock records or rows you need.
Result preview
Check the structure before download or before saving the profile.
Recurring workflows
After signup, the profile can run manually or on schedule and deliver output to the right channel.
JSON → YML FAQ
Convert JSON to YML and automate repeat exports
Start with a structure check, then save a profile for catalogs, price lists, stock data and integrations.
Try for free → Up to 5 MB free · up to 2 GB after signup · no software install