Network capture of a Compress PDF run

Captured on 19 October 2026

This page holds a sanitized network capture from one run of the Compress PDF tool on yourpdfutils.com. It is a later run on 19 October 2026, in headless Chrome 154, on one site. The 18 October test described on the upload test page used Chrome 155 across 11 sites. This capture is published so you can look at the requests yourself instead of trusting a summary.

Download compress-pdf-network-capture.har (standard HAR 1.2 format, opens in your browser's developer tools or a HAR viewer). It is sanitized: the 18 consent request bodies are truncated to 500 characters, response contents are not recorded, and sizes are kept.

What we did

• Opened https://yourpdfutils.com/compress-pdf in headless Chrome 154 with network recording on. The capture covers the page and the tool frame it loads. It may not include all worker or beacon traffic.
• Attached a synthetic 70 KB test PDF made for this test. It contains no personal data. The exact test file is not published.
• Clicked Process and let the tool run to completion. The file was already small, so the tool declined to replace it: the output would have been larger than the input. This capture therefore does not cover a successful compress-and-download run.
• Recorded every network request the browser made from page load until after the run finished.

What the capture shows

• 54 requests in total.
• Every request to yourpdfutils.com is a GET for page assets (the page, JavaScript, icons), except one 834-byte POST to /cdn-cgi/rum, which is Cloudflare's standard performance-telemetry endpoint. That is the only non-GET request to our own domain.
• The other requests go to Google ad, consent and font services, plus one Google reCAPTCHA frame and one local blob: address used by the page itself. Several of the Google ad and consent requests are POSTs with small bodies. The site is ad-supported, so ads load as on any page. The largest single request body in the session is about 4.3 KB, an ads ping.
• The test PDF is about 70 KB. In this run, no request body was close to the file's size.

Method limits

• A capture shows what this browser sent during this one run on 19 October 2026. It cannot show what happens in every session or after future code changes.
• The body-size check can miss data hidden inside chunked, compressed or encoded uploads. That is why we publish the request list in the file instead of a summary. You can inspect the requests it contains, within the sanitizing limits above.
• The test is easy to repeat: open the same page, open your browser's developer tools, switch to the Network tab, and run the tool with any file.