PDF Tools

What the Nesake PDF toolkit does

PDF is the format documents end up in when they need to look the same everywhere — a contract, an invoice, a scanned form, a set of slides. That reliability comes at a cost: PDFs are awkward to change. Splitting one page out of a fifty-page scan, stitching three quotations into a single attachment, or squeezing a 30 MB brochure under an email limit are all trivial jobs that somehow require software.

The Nesake PDF toolkit covers those everyday jobs in one place: merge several PDFs into one file in the order you choose, split a document into individual pages or ranges, rotate pages that were scanned sideways, reorder or delete pages, and compress a file so it travels well over email and messaging apps.

Everything runs in the browser. Your document is parsed, edited and re-written by JavaScript on your own machine — there is no upload step, no processing queue, and no copy of your file sitting on a server waiting to be deleted by a retention policy you cannot see.

Merging PDFs without losing quality

Merging is a structural operation, not a re-render. The page objects from each source document are copied into a new document with their fonts, vector paths and embedded images intact, so text stays selectable and searchable and image pages keep their original resolution. Nothing is rasterised, and nothing is re-compressed unless you explicitly ask for compression afterwards.

The most common use is assembling an application pack: an ID scan, a proof of address, a signed form and a photograph, all delivered as one attachment because the recipient asked for a single file. Order matters, so arrange the documents before merging rather than fixing it afterwards.

Splitting and extracting pages

Splitting is the inverse operation. You can break a document into one file per page, or pull out a specific range — pages 4 to 9 of a lease, the invoice page from a bundled statement, a single certificate from a batch scan. Extracted pages keep their original content exactly; only the container changes.

This is also the safest way to share part of a document. Rather than sending a whole medical or financial file and asking the recipient to ignore the rest, extract the pages that are actually needed. Redaction by omission is far more reliable than redaction by trust.

Compressing a PDF sensibly

Most oversized PDFs are large because of images, not text. A scanned page at 600 DPI in full colour can be several megabytes on its own, and a twenty-page scan quickly becomes unmailable. Compression works by re-encoding those embedded images at a lower resolution or a higher JPEG compression ratio while leaving the text layer untouched.

Pick the level to match the destination. For email attachments and web uploads, aggressive compression is usually invisible on screen. For anything that will be printed, or any document with small print that must remain legible after enlargement, stay conservative — once detail is discarded it cannot be recovered from the compressed file.

• Email attachment limits: most providers cap at 20–25 MB per message.
• Government and bank portals: often demand under 2 MB per document.
• Job applications: a 500 KB CV opens instantly on any connection.
• Archival copies: keep the uncompressed original alongside the shared version.

Privacy, offline use and limits

Because every operation is local, the toolkit works offline once loaded and imposes no page count or file size limits beyond what your device's memory can hold. Confidential material — contracts under NDA, payslips, identity documents, patient records — never crosses the network.

The practical limit is memory. Very large scans, in the hundreds of megabytes, can exhaust a phone browser; the same file will usually process fine on a laptop. If a merge fails on mobile, split the job into two smaller merges and combine the results.

Frequently asked questions