Input
- Up to 12 PDF files, 20 MiB each and 50 MiB combined
- Up to 500 pages across the selected documents
- Unlocked PDFs that the browser can parse locally
PDF submission
A page-correct PDF prepared for a submission portal.
Merge, reorder, rotate, compress, and inspect document metadata before export.
01
1. Add files
Choose or drop files after the local workspace opens.
02
2. Set the result
Choose the output format and limits after opening the workspace.
Processing plan
- Arrange pages
- Fit the limit
- Verify and export
Save your settings on this device for reuse. Presets do not include files or their contents.
File controls load after an explicit action. Processing and downloads stay in this browser tab.
Worked example · Prepare a submission while preserving the source
Worked example
Prepare a submission while preserving the source
Rehearse with a synthetic document before handling an application. Write down the required pages, order, format and byte limit. The browser can prepare a file, but it cannot approve the application or certify that the document satisfies the receiving organization.
- Input and settings
- Required pages and order · recipient byte limit
- Expected output
- One reviewed PDF · actual pages and bytes checked
Steps to reproduce
Select the required pages, review the assembled document and use the available size-reduction options only when needed. Keep the original and inspect any warning about a change in representation. Download only after checking the result status.
Check before you use it
Check page order, fine print, links and any features important to the recipient. If the target cannot be reached without unacceptable loss, keep the source and ask the recipient for an alternative submission route. Local preparation avoids uploading the working file to Toolars; sending the final file to a portal is a separate action under that portal’s rules.
What this PDF workspace accepts and produces
Output
- One merged PDF in the page order shown in the workspace
- Selected rotations, removed pages, compression, and supported document-info cleanup
- A reopened result with page count, actual bytes, and supported metadata checked again
- A byte-gap report, quality review notes and next steps based on the completed compression attempt.
Local processing boundary
Files, thumbnails, page operations, compression, verification, and download remain in this browser tab. Toolars analytics and storage do not receive file names, PDF bytes, settings, metadata values, or results.
Visible test method
The release benchmark merges two synthetic PDFs, changes order, removes one page, rotates another, compresses, clears supported document information, downloads the result, and opens it again for verification.
- Validate file, batch, and 500-page limits before running the operation chain.
- Apply the displayed page order and rotations, then compress and remove supported document information.
- Reopen the output, verify page count and actual bytes, inspect supported metadata, and release the download only after those checks.
Important limitations
- The target first triggers structural optimization. Image-page conversion is tried only when text preservation is not required, at 150 DPI with JPEG quality 85%, 75%, 65%, then 55%. At most five candidates are attempted under a 60-second cooperative cancellation budget; an active engine call can take longer to stop.
- The size ceiling is a goal, not a guarantee; a larger output is labeled as the closest verified result.
- Strong compression first tries structural optimization. If the selected result uses image-page conversion, previously selectable text becomes part of the images and is no longer searchable; check the result before submitting.
- Metadata verification covers the PDF document Info dictionary, not every possible XMP stream or embedded file.
- Encrypted or damaged PDFs need a valid unlocked source; device memory limits may require a smaller batch. An image-only PDF is accepted if it can be parsed, but this workflow cannot make its text searchable.
- File size does not prove readability, working document features or acceptance by the submission portal.
Common failures and recovery
The PDF is damaged or password-protected
Remove it and choose a valid unlocked PDF. Toolars does not attempt to bypass document protection.
The file or page limit is exceeded
Reduce the number, size, or pages of the selected PDFs and run again.
The size target is not reached
Keep the closest verified result, raise the limit, use Strong compression, or remove pages and retry.
The browser runs out of memory
Close unused tabs, reduce the batch or page count, and retry on this device.
PDF submission FAQ
How do I put page 3 first?
Add a three-page PDF. Move the original page 3 earlier twice, then prepare the PDF. Inspect the download: original pages 3, 1, 2. Keep the original for comparison.
How do I prepare a PDF for a 2 MB limit?
If the portal means 2,000,000 bytes, try 1.90 MiB. Choose structural optimization to preserve text and prepare the PDF. Check actual bytes and readability; a closest result may exceed the limit, and meeting the size target does not guarantee acceptance.
Are PDFs uploaded to Toolars?
No. The operation chain and verification run in the active browser tab.
Does the workspace guarantee my portal will accept the PDF?
No. It verifies the configured size, page count, and supported metadata fields; a portal may enforce additional rules that it does not publish.
Can I add photos directly?
Not in this workflow. Convert images with the related Images to PDF tool first, then add the resulting PDF here.