Control DOCX render output, PDF conversion, base64 metadata, and filenames.

Overview

Control DOCX render output, PDF conversion, base64 metadata, and filenames. 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

• A template can render directly to DOCX.
• asPdf requests a PDF after DOCX generation.
• A template output setting may also select PDF conversion.
• metadata=true returns base64 content and signature metadata in JSON.
• Binary responses include a content type and attachment filename.

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

• Convert DOCX to PDF
• 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.