On this page
Group workbooks by output purpose
Process summary dashboards separately from detailed registers. They often need different fitting choices even when both use ODS. Archival workbooks may also require PDF/A-1b and maximum image fidelity.
A shared PDF page range applies independently after each workbook is paginated, so it should only be used when files have a consistent report structure.
Keep file-level progress and retry states
Each workbook should move through upload, rendering and completion independently. One malformed or unsupported file must not hide PDFs that completed successfully.
Review the failure message before retrying. Repeated errors can point to a damaged package, an unsupported embedded object or unavailable conversion capacity.
Verify representative and exceptional sheets
Preview each high-value output and sample normal batch items. Check the widest sheet, the longest table, the chart-heavy dashboard and any workbook that uses uncommon fonts or form controls.
- Confirm sheet order and page count.
- Review totals and formula results.
- Inspect charts, labels and page edges.
- Download individual files or the completed ZIP.
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 ODS to PDFFrequently asked questions
Clear answers before you merge
Does one failed workbook block the batch?
No. Successful PDFs remain available and failed files can be retried.
Can completed results be downloaded together?
Yes. Multi-file results can be downloaded as a ZIP.
Should every batch use one-page-per-sheet?
No. Use it only when each sheet remains readable after scaling.
