Skip to content
iLoveDoc logo

iLoveDoc

Merges, splits, compresses, converts and edits PDF files in the browser, processing files locally without uploading them to a server.

Actively maintained

At a glanceswept Oct 22, 2026

≈ 21visits/mo

Emerging · estimate, read Oct 22, 2026

  • iLoveDoc21
  • #1 Coda3.6M
Activity
Actively maintainedsite updated yesterday
Used for
  • combine several PDF files into one document
  • reduce PDF file size without losing much quality
  • convert PDFs into editable Word documents
Worth knowingcomputed from what we read · each with its source
  • Publishes llms.txt, a file written for AI assistantsilove-doc.com ↗
  • Launched on Product Hunt on Oct 22, 2026Product Hunt ↗
Your datawhat they publish, each line with its page · read Oct 22, 2026

These are iLoveDoc's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

Most used in Documentsby use, among tools still maintained — this tool shares no tags yet

Figure and bar: visits/mo, estimate · year: online since

Compare iLoveDoc with

Pick up to two.

All Documents tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use iLoveDoc for?

Sign in to leave a note
Questions this page answers
  • What is iLoveDoc?

    Merges, splits, compresses, converts and edits PDF files in the browser, processing files locally without uploading them to a server. It is listed in the Atlas under Documents.

  • Do people use iLoveDoc?

    Emerging: ≈ 21 visits/mo · estimate, 2026-10.

  • Is iLoveDoc still maintained?

    Actively maintained: site updated yesterday.

  • Is iLoveDoc safe?

    We do not audit vendors. What iLoveDoc publishes, read 2026-10-22: GDPR stated on its privacy policy.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk