We tested PDF Linx's merge and compress tools: what the page says and what we saw
In our test on 16 November 2026, PDF Linx merged and compressed our test PDFs correctly, and we saw no upload request carrying our files. The site's own pages describe processing in two different ways, so we explain exactly what we did and did not check.
How we tested
- Test date
- 2026-11-16
- Tool
- PDF Linx
- Version
- No version number or update date is shown on the pages
- Environment
- Chromium 159 via Playwright 1.65.1 on Windows 11; fresh browser profile for each run
Method:
- Tool: PDF Linx (pdflinx.com), Merge PDF and Compress PDF pages.
- Test files: PDFs we generated ourselves, with no personal data. Each contains a unique marker string so we could search for it. Two small files (3 and 2 pages, about 57 KB each) and one 2-page file of 1,678,621 bytes with embedded noise images.
- Viewports: Desktop 1280 px wide, phone 375 px wide, and one run with the network switched off after the page had loaded.
- What we did not use: accounts, paid plans, AI features, ads or any download.
Merge PDF
We merged the 3-page file and the 2-page file. The result was a 109,634-byte PDF with 5 pages in the right order (pages 1–3 from the first file, 4–5 from the second). Both marker strings and the Chinese and accented characters were present in the output. The "Download" button appeared in under a second in all three runs. Nothing needed an account, and we saw no watermark.
Compress PDF
We compressed the 1,678,621-byte file with the page's default settings. The output was 982,127 bytes (about 41.5% smaller; the page itself showed "1.60 MB → 959 KB"), still two pages, and it opened normally. The button appeared after about 1.4 seconds on desktop. We did not check which compression option was selected by default, so we cannot say which level this represents.
What the network log showed
Across six runs (merge and compress, on desktop, phone width and offline), we recorded every request. None had a request body, and none contained our marker strings or the bytes of our test files. The only third-party requests were to Google Tag Manager and Google Analytics, plus cdnjs.cloudflare.com on the compress page. With the network switched off after the page had loaded and the files had been chosen, both tools still produced their output.
What this does and does not show: it shows that, in these runs, we saw no upload from the browser. It does not show what the company's servers do, because we can only see what the browser sends. We did not test service workers or WebSockets separately, and we did not test loading the page for the first time while offline.
What the site says
The site describes processing in different ways on different pages:
The compress page's footer reads "Processed in your browser".
The merge and compress pages each read "Files are processed on secure servers and automatically deleted after 1 hour."
The compress page shows both "Max 10 MB" and "No file size limit".
The compress page footer reads "No tracking", and our log shows requests to Google Analytics and Google Tag Manager.
We cannot tell which description matches what happens on the server side. Our test only covers what the browser did.
What to take from it
If you need to merge or compress a PDF and the file is not sensitive, both tools worked in our test, and the output was correct. If the file is sensitive, do not rely on any site's wording, including ours: run the same check yourself (see our guide to checking that a file tool does not upload your files) or choose a tool whose design guarantees it.
Related
Disclosure
Keel has similar tools (Merge PDF and Compress PDF), so we have an interest in this topic. We did not use affiliate links, and we have no relationship with PDF Linx. We tested only what is described above, and we will correct this article if the site changes or if you show us something we missed.
No affiliate links are used on this page.
FAQ
Did PDF Linx upload our files in the test?
We saw no request that carried our files or marker strings in six browser runs. We cannot say what happens on the company's servers.
Did the tools need an account?
No. We did not sign up for anything, and we saw no paywall, login wall or watermark in the runs described above.
Can I repeat the test?
Yes. Open your browser's developer tools, go to the Network tab, clear it, process a file, and look for requests that carry the file. Our guide explains the steps.