Tool guide

Choosing the Right Tool — and What to Expect

Start by picking the right product line: document, image, and file work lives on PDF & Image Tools, network diagnostics live on Network Tools, and All Tools lists everything in one directory. This page then covers how the document-side tools are grouped, real limitations worth knowing before you start, and practical steps if something doesn't work the way you expected.

The four categories on PDF & Image Tools

Every tool on PDF & Image Tools falls into one of four categories:

Known limitations worth knowing before you start

These are real, current limitations, not hypothetical edge cases:

Size and device considerations

Because browser-local tools use your own device's memory and processing power, very large files — or older, lower-memory devices, including many phones — may process more slowly or fail where a desktop browser with more available memory would succeed.

Each tool page states a guideline file size. Treat it as a practical ceiling rather than a guarantee: actual available browser memory varies by device, and by how many other tabs or apps you have open at the same time.

Why your output file might look slightly different from the original

Format conversion is inherently lossy in specific, explainable ways: fonts not embedded in the source file may be substituted; some formats don't support features the other format has, so those are dropped or approximated; and complex layouts — multi-column text, embedded objects, unusual table structures — don't always translate one-to-one. This isn't a defect specific to NexKit; it's inherent to converting between different file formats in general.

If a tool doesn't work

A few practical steps, roughly in order: