Convert an uploaded DOCX file to PDF without applying a FeraRender template.

Overview

Convert an uploaded DOCX file to PDF without applying a FeraRender template. Document formats have different failure modes. Confirm whether the workflow transforms data, fills an existing form, packages OpenXML, or only converts a file.

Key points

• Upload the file using the supported multipart field.
• Use a .docx extension or the DOCX MIME type.
• LibreOffice is the primary conversion engine.
• Windows may fall back to Microsoft Word.
• Read conversion metadata headers for engine and version.
• Handle conversion errors as non-retryable until the engine or source file is corrected.

Example

curl --request POST "<confirmed-docx-pdf-route>" \
  --header "x-auth-token: <token>" \
  --header "instance: <instance-uuid>" \
  --form "file=@document.docx" \
  --output "document.pdf"

Replace bracketed values with values issued for the target environment. Never place production tokens, API keys, or client data in screenshots or public examples.

Recommended procedure

1. Choose the exact PDF or DOCX workflow.
2. Validate the source template or file.
3. Submit representative data with the expected response mode.
4. Open the resulting file and verify layout, fonts, fields, and metadata.

Troubleshooting

The PDF is blank or malformed

Validate the transform output or field mapping before blaming the conversion engine.

Fonts or pagination differ

Install required fonts and test with the same conversion engine used in production.

Conversion fails for one file

Open and resave the source DOCX, remove unsupported content, and compare it with a known-good file.

Related documentation

• Render DOCX as PDF or Metadata
• Literal OpenXML Package Generation
• OpenXML Package Manifest Reference

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.