ONIX Metadata Generator
Fill in a book metadata form and get a checked ONIX 3.0 XML file with ISBN-13 validation, prices, subjects and a live preview.
Book
Print editions usually need a page count.
Contributors
Add at least one contributor with a name.
Publishing
WORLD, or country codes separated by spaces, such as US CA GB.
Subject codes
No subject code. Most retailers and distributors ask for at least one BISAC or Thema code.
The first code of each scheme is marked as its main subject. Look codes up in the BISAC or Thema lists; this tool checks the pattern, not whether the code exists.
Description
0 / 350
No description. Retailers normally show it on the product page.
Prices
No price. A price is usually needed for a product that is on sale.
Checks
- Enter the title.
- Add at least one contributor with a name.
- Enter the ISBN-13.
- Enter the publisher name.
- Enter the publication date.
- Print editions usually need a page count.
- No subject code. Most retailers and distributors ask for at least one BISAC or Thema code.
- No description. Retailers normally show it on the product page.
- No price. A price is usually needed for a product that is on sale.
Retailers and distributors differ in the ONIX fields, code lists and versions they accept, and this tool does not check the file against any one of them or against the full ONIX schema. Check the target distributor's own ONIX requirements before you send the file.
ONIX 3.0 XML preview
The XML appears here as soon as the required fields above are valid.
About ONIX Metadata Generator
Builds an ONIX 3.0 metadata file for a book from a form: title, contributors, ISBN-13, publisher, publication date, language, subject codes, description, prices, product form, page count and series. Fields are checked as you type, including the ISBN-13 check digit and the date.
Fill in the form. Anything that is wrong is listed under the field and in the summary, and the XML appears once the required fields are valid. Read the preview, then copy it or download the .xml file.
ONIX is a shared format, but retailers and distributors each ask for different fields and code versions. Before you send the file, read the target distributor's own ONIX or metadata requirements and compare them with what this tool wrote.
- How is the ISBN-13 checked?
- The tool removes hyphens and spaces, requires 13 digits starting with 978 or 979, and recomputes the check digit by weighting the first 12 digits alternately by 1 and 3. If the last digit does not match, it tells you what it should be. An ISBN-10 is rejected with an offer to convert it.
- Which date formats can I use?
- Use YYYY-MM-DD, for example 2026-03-15. YYYY-MM and YYYY are also accepted for a month or a year only. The date must exist on the calendar, so 2025-02-29 is rejected. The XML carries it without hyphens, with the matching ONIX date format code.
- Will a retailer accept this file?
- The tool cannot promise that. ONIX is a shared standard, but each retailer and distributor sets its own required fields, code lists and ONIX version. The file is not checked against the full schema or any one platform, so read the target's metadata requirements and compare.
- What are BISAC and Thema codes?
- They are two subject classification schemes. BISAC codes are three letters and six digits, such as FIC027020, and are common in North America. Thema codes are short, such as FBA or 1KBB, and are used more widely abroad. The tool checks the pattern only; look up the right code in the official lists.
- Can I add more than one price or contributor?
- Yes. Add a price for each currency, each with its own price type, and as many contributors as you need as author, editor, illustrator or translator. The tool refuses two prices with the same currency and type, and it marks the first code of each subject scheme as the main subject.
How to use ONIX Metadata Generator
Enter the title, contributors, ISBN-13, publisher, publication date, language, product form and page count, then add subject codes, a description and one or more prices. Problems are shown under the field and in the Checks list. When the required fields are valid the ONIX 3.0 XML appears; copy it or download the .xml file.
When to use it
Use it when a distributor, aggregator or retailer asks for an ONIX file and you have no metadata system, or when you want to see what a basic ONIX 3.0 record for one title looks like. It covers a single book: print or EPUB, several contributors, BISAC and Thema codes, series and several currencies.
When not to use it
Do not use it to manage a catalog of many titles, to send feeds automatically, or for ONIX 2.1 or other releases. It writes one product per file and no cover or audio resources.
Tips for best results
Copy the ISBN straight from your ISBN account, with or without hyphens. Use a separate ISBN for each format. If the publication date is in the future, set availability to Not yet available. Keep the description plain text and read the XML once before sending it.
Limitations
The ISBN check digit, date, price format, code patterns and field lengths are checked, but the file is not validated against the EDItEUR schema or any retailer's rules, and BISAC and Thema codes are checked by pattern, not looked up. Retailers differ in the fields and code lists they accept, so check the target distributor's own requirements before sending the file.
Privacy
The form is processed in your browser tab and the XML is built there. Nothing is uploaded or stored, and the data is gone when you close or reload the page.
More from File & Misc: