Blog post

Direct-download PDF tool benchmark from April 28, 2026

Simulated test results for 20 We Want PDF direct-download tools. The numbers come from a test environment and do not represent real-world processing times.

Updated

The numbers in this article come from a simulated test environment and do not represent real-world processing times. On April 28, 2026, we ran 20 direct-download We Want PDF tools against a stand-in processing service with a fixed delay, so the results only compare overhead between tools under identical, artificial conditions.

What “direct-download” means

A direct-download tool returns the finished file in the same request you send it. You upload, wait a moment, and the download starts. Tools such as Split PDF, Compress PDF, and PDF to Word work this way. Slower tasks run as queued jobs instead; see the queued PDF job benchmark.

How the test was set up

  • 20 direct-download tools were tested.
  • Each tool was run 3 times.
  • The real PDF processing step was replaced by a stand-in service that waited a fixed 75 ms before answering.
  • Supporting services ran in memory on the test machine.

Because no real document was processed, these timings say nothing about how long your own file will take. File size, page count, scanned images, and the tool you choose all change real processing time far more than anything shown here.

What the simulated results show

  • 18 of the 20 tools had median times between 92.22 ms and 97.32 ms in the test environment.
  • JPG to PDF (109.37 ms median) and Merge PDF (111.32 ms median) were slightly above the rest.
  • Merge PDF had one slow run of 1,974.18 ms, which pulled its average up to 729.41 ms. This is why the table shows the median and maximum alongside the average.

Selected rows (simulated)

ToolAvgMedianMinMax
split-pdf92.53 ms92.22 ms90.99 ms94.38 ms
compress-pdf103.04 ms94.21 ms89.48 ms125.43 ms
pdf-to-word99.43 ms97.32 ms90.27 ms110.71 ms
jpg-to-pdf107.18 ms109.37 ms95.61 ms116.56 ms
merge-pdf729.41 ms111.32 ms102.73 ms1,974.18 ms

Download the data

The CSV contains one row per tool with the run count, the fixed stand-in delay, and the average, median, minimum, and maximum timings. More context is on the research page.

How to read these numbers

Treat this data as a comparison between tools under the same simulated conditions, not as a speed claim. It should not be quoted as real-world performance or compared with other PDF services.

Trust center

Trust pages

How We Want PDF handles your files: privacy, security, and how long uploads are kept.

privacy

Privacy

How We Want PDF handles the files you upload, what is needed to use the tools, and which tools send content to an AI provider.

Read page
security

Security

How We Want PDF checks uploads, delivers results, limits abuse, and removes queued job files.

Read page
retention

File retention

How long We Want PDF keeps uploaded files and results, and when they are removed.

Read page