On this page
Use one profile for documents with the same purpose
Group files that share the same delivery requirement. A set of archival records may use PDF/A-1b and maximum fidelity, while ordinary review copies may use the professional profile.
Page ranges apply independently to each file. Before using a shared range, confirm every document contains those page numbers.
Keep processing and failures visible
Each file should report upload, processing, completion or failure independently. A failed item must not hide PDFs already created successfully.
Retry only failed files after checking the error. Repeated failures can indicate a damaged ODT package, unsupported extension content or missing conversion capacity.
Verify representative and exceptional documents
Preview every high-value output and sample ordinary files across the batch. Pay extra attention to the longest document, complex tables, uncommon fonts and files with comments or form controls.
- Confirm expected page counts.
- Inspect first and last pages.
- Test bookmarks and important links.
- Download individual PDFs or the completed ZIP.
- Retain source files until delivery is accepted.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try ODT to PDFFrequently asked questions
Clear answers before you merge
Does one failed ODT block the complete batch?
No. Files retain independent states, and successful PDFs remain available.
Can failed files be retried?
Yes. Use the retry action after reviewing the per-file error.
Can completed PDFs be downloaded together?
Yes. A completed multi-file batch can be downloaded as a ZIP, while individual downloads remain available.
