Initializing secure environment…
Initializing secure environment…
The terms governing use of ihatepdf, written to be read rather than to be impenetrable. They cover what you may do with the tools, the intellectual-property position on the document-processing and compression engines, the disclaimers that come with running code on your own device, and the limits of what a free site can promise. No registration is required to use anything here, so these terms are not a gate — they are a description of the arrangement.
These are the terms of use for ihatepdf, including the intellectual-property terms covering the document-processing and compression engines. Nothing here requires an account, and every tool is available under them immediately.
Because document processing and compression are areas where broad patent claims have historically been asserted, and where a free tool's users are right to ask what is being claimed. The honest position is that the methods here are implemented in long-standing open-source libraries under open licences, and that this site claims no ownership over them. Being clear about that is worth more than a paragraph of boilerplate.
It means check important output rather than trusting it. A repaired PDF may have lost pages, and the report says so. A compressed file may not have reached the target, and the tool says that too. A converted table may have shifted a column, and the preview exists. The disclaimers and the design features point at the same thing: verify before you rely.
You keep every right you had in your document, and you gain no rights in anyone else's. The tools are neutral about content. That is worth stating because a service that processed files on a server would be in a different position — and one reason the architecture and the legal position line up here.
The parts of any terms that affect you are usually three: what happens to your data, what you are responsible for, and what happens if something goes wrong. On a site where nothing is transmitted and nothing is stored, the first is short. The second is your document. The third is a disclaimer — which is why keeping your original file is the practical advice that follows from reading this page.
No, and there is no way to create one. The tools are available immediately to anyone who opens the page. Terms that describe an account you do not need are, in this case, descriptive rather than conditional.
The engines are third-party open-source projects — pdf-lib, pdf.js, Tesseract and the Whisper implementation among them — each under its own licence, bundled locally rather than fetched at runtime. This site claims no ownership over them and grants no rights in them beyond what their licences grant. What is described here is the position, not a grant of new rights.
Yes, with the usual caveat that your output can only contain material you had the right to use in the first place. A tool cannot confer rights over a document you did not own, and nothing here creates any.
The tools are provided as they are, without warranty of any kind, which is the standard position for free software and is stated here plainly rather than hidden in small print. Practical consequence: keep your original file, and verify anything that matters. The recovery report on a repaired PDF and the measured size on a compressed one both exist for exactly this reason.
To the maximum extent the law allows, no liability for loss arising from use of a free service provided without warranty. This is a site funded by nobody, run by people who are not compensated for it; a liability position that outstrips that reality would be a fiction.
Yes. Personal and commercial use, with no licensing fee, no per-seat cost and no account. Several businesses use the tools specifically because client documents stay on their own machines.
Process only documents you have the right to process, do not attempt to use the site to distribute or host material, and do not rely on it as infrastructure for a service of your own. There is no upload and no storage, so there is very little that could be abused — the honest constraint is the legal one, not a technical one.
The privacy boundary is different and is documented in the tools themselves: the raw file is never uploaded, but text extracted from it is sent to the model provider you supply a key for. That is a disclosure to a third party under your own key and your own provider's terms, and it is stated at the point of use rather than only here.
More about this site — all free, no upload.