Journal XML

PDF and Word to JATS XML.
A clearer journal handoff.

Give your journal content a structured next step. Start with a born-digital PDF or a Word document, review the result, and publish XML for the workflow that follows.

For journal production teams, scholarly publishers, and professionals preparing structured article content.

A closer look

What makes the output useful.

Choose the right source

When you have a well-structured Word manuscript, begin there. If the print PDF is your available source, use a born-digital file with real text.

Review article relationships

Check author affiliations, section hierarchy, figure and table references, and bibliographic links. Structure carries meaning between systems.

Validate for the destination

A valid XML document can still miss a receiving platform’s rules. Confirm the required schema, metadata, and asset package with that platform.

Match the workflow to the job

Prepare the article for its destination

For journal production teams, scholarly publishers, and professionals preparing structured article content.

Source or requirementWhat to checkWhy it matters
Word manuscriptsUse consistent heading styles, real tables, and clear references.A structured source makes the intended article relationships easier to review.
Born-digital article PDFsInspect columns, reading order, figures, captions, and reference links.Print layout alone does not define the structure of JATS XML.
A journal platform or archive handoffConfirm the required JATS version, metadata, assets, and receiving-system rules.Schema validation does not guarantee acceptance by a particular destination.

For recurring journal work, evaluate articles with different tables, reference styles, and layouts. Agree on metadata and validation requirements with the receiving platform, then plan your monthly article volume and team capacity.

From upload to delivery

How the conversion works

01

Choose PDF or Word input

Upload the journal article and choose XML output. Use born-digital PDFs or supported Word documents; Word input does not produce EPUB or accessible PDF.

02

Review article structure

Check metadata, sections, authors and affiliations, references, tables, and figures. Confirm the relationships needed by your publishing workflow.

03

Publish and check the handoff

Download the XML output and inspect its validation results. Check the required asset package and recipient-specific rules before submission.

For professionals & teams

Choose capacity for the work ahead.

Try a representative document free. Individual is for one professional; Team supports up to 10 users. Compare page allowances and daily limits before choosing a monthly or annual paid term.

Paid plans are fixed-term purchases with no automatic renewal. SDK access and licensing are separate.

A few good questions.

Does a Word upload also create EPUB or accessible PDF?

No. Word input is supported for XML, JSON, and Markdown. For EPUB or accessible PDF, start from a born-digital PDF.

Is this a guarantee of acceptance by an archive or journal platform?

No. Each destination can impose additional rules. Review its current requirements and validate a representative article before a bulk handoff.

Is JATS the same as a PDF with selectable text?

No. JATS describes article content with named XML elements and attributes. Selectable text alone does not encode article structure or relationships.

Should I use JATS for books?

JATS is designed for journal articles. BITS is a related book model; confirm the format your receiving workflow requires before choosing an output.

Keep learning: From Word to JATS XML: prepare a cleaner journal handoff.

Your next chapter starts here.

Bring one born-digital PDF. Explore the result, review the details, and see what your next edition could be.

Start converting free