Unlock a PDF without uploading it anywhere

Q: What is the difference between the two passwords?

A PDF has room for two. The user password is the one a reader asks you for; without it the file does not open. The owner password lifts the restrictions - printing, copying, editing - and a document very often has an owner password with no user password at all, which is why it opens for everybody and still refuses to print. This tool accepts either one, and tells you which of them the document actually let it in with.

이 약속을 직접 확인하는 방법

Most protected PDFs are not locked at all, and this page says so before it does anything. A PDF can carry two quite different things. An open password is real: without it the file cannot be read, and nothing here will find one. Restrictions — no printing, no copying, no editing — are not. A file carrying only those opens for anybody, which means it has to contain everything needed to derive its own key, because your reader derived it. What stops the reader printing is a permissions field inside the document, honoured by agreement between well-behaved programs. Adobe documented that from the beginning. Removing it is not breaking anything; it is declining to volunteer. The page tells you which of the two you have, and only asks for a password when there is genuinely one to ask for.

It does not guess passwords, and there is no loop in it that could. If a document has an open password, you supply it or the document stays shut. There is no dictionary here, no word list, and no attempt on the 40-bit keys of the 1990s that really would fall to a search. That is a deliberate line rather than a limitation nobody got round to: a page that quietly tried a few million passwords for you would be a different tool with a different name, and it is not this one. Both the password that opens a document and the owner password that lifts its restrictions are accepted, because either one is a password you were given.

The password is typed here and used here. What you type goes into a key derivation running in this tab and nowhere else. It is not stored, not remembered between files, and not written to the address bar, and the page's Content-Security-Policy names every address this page may contact — not one of them belongs to this site. A tool that asked for a document password and then made a network request would be doing the single worst thing a tool of this kind can do.

The finished file is opened again, here, before you are offered it. Everything above is this tool marking its own homework until that happens. So the bytes that are about to become your download are handed to the same reader that the compressor, the merger and the redactor use — a reader that refuses an encrypted document outright — and it has to open with no password and come back with the same number of pages. A file that still had any encryption on it could not pass that. If it does not, the run is reported as failed and there is no download.

The pages themselves are not re-rendered, re-encoded or reflowed. What changes is the encryption around the document, not the document. Every page's drawing instructions, every embedded font and every picture is written back out exactly as it arrived, so text stays selectable and searchable, scans stay at the resolution they were scanned at, and nothing shifts on a page. The one thing that does change is what a rewrite always changes: older superseded copies of objects left behind by earlier edits are not carried over, which usually makes the file a little smaller.

A digital signature cannot survive this, and the page says when there is one. A signature covers the exact bytes of the file it was applied to, so any rewrite invalidates it — that is what a signature is for. This tool writes a new file, so the copy you get back is unsigned, and it says so on the results when it finds a signature to warn about. Your original is still the signed one. There is no way round this and no tool that has one.

It says what the protection was actually worth. A document locked with 40-bit RC4 in 1998 and one locked with AES-256 last year both say "password protected" in a reader, and they are decades apart. The page names the scheme, the key length and the revision, and says plainly which of them are broken, which are merely superseded, and which is current. That is worth knowing about a file you were told was secure, and no reader shows it to you.

Certificate-locked documents are turned away rather than half-opened. Some documents are encrypted to a certificate rather than a password — the corporate kind, where the key lives in a smart card or a key store. Those are refused with a message saying what they are. Nothing typed into a password box can stand in for a private key, and pretending otherwise would waste your time.

What Google loads, and what it is not given. The ad and measurement scripts come from Google. Neither is handed anything about your document: not a file, not a page, not a name, a size, a page count, a password, or what the file was protected with. Every line that reads, decrypts or writes a PDF is served from this origin and listed in the repository.

What the donate button loads, and what it is not given. The "Buy me a coffee" button in the header is drawn by a script from cdnjs.buymeacoffee.com and letters itself from Google Fonts. It is a link and nothing more: it reports no visit, and it is handed nothing about you or your documents. Nothing happens unless you click it, and what you would be clicking through to is somebody else's site.

It works offline. Disconnect from the network and everything on this page still functions. That is the simplest proof of all: a tool that sent your document away to be unlocked would stop.

직접 확인해 보세요. 위에 적은 어느 것도 그냥 믿으실 필요는 없습니다. 이 페이지는 저장소 안의 템플릿과 설정을 빌드 스크립트가 찍어 낸 결과이고, 그 스크립트는 누구나 읽고 직접 돌려 볼 수 있습니다. 결과물은 dist 브랜치에 그대로 올라가 있고요. 그래서 실제로 제공되는 파일과 소스를 빌드한 결과를 나란히 놓고 비교해 보실 수 있습니다:

github.com/A-Box-of-Tools/website

먼저 읽어 볼 파일을 꼽자면, Content-Security-Policy는 config/site.toml, src/crypt.js for how a password becomes a document's key — and for the fact that there is no loop in it anywhere — and src/aes.js and src/rc4.js for the two ciphers themselves. None of them can reach the network, and neither can the reader or the writer beside them.

회사 보안 소프트웨어가 업로드를 경고한다면. 그것은 브라우저에서 파일이 선택되는 순간을 지켜보며, 페이지가 그것을 보낼 생각인지는 알 수 없습니다 — 그래서 고르는 순간에 경고합니다. 여기서는 아무것도 보내지 않습니다. 브라우저 개발자 도구를 열고 네트워크 탭으로 옮긴 뒤 파일을 골라 보세요. 그것을 실어 나르는 요청은 없고, 이 페이지 자체의 로컬 미리보기 말고는 요청 자체가 없습니다. 같은 확인을 IT 팀도 삼십 초면 할 수 있습니다.

1 Choose the protected PDF

Drop your protected PDF here or click to browse — one document at a time

2 See what is on it

A PDF can be locked in two ways that look alike and are not. One is an open password, which nobody can get past without the password. The other is a set of restrictions — no printing, no copying, no editing — on a file that opens for everybody, where the lock is a request your reader has agreed to honour rather than anything cryptographic. This says which of the two this document has.

Nothing chosen yet. Once a document is here, this will say which of the two it has, what the encryption is worth, and whether a password is needed at all.

3 Take the protection off

Also take out what the file remembers about where it came from The name of the program that locked it, when it was made and last edited, the XMP packet and the private blocks a layout application leaves behind. This is a separate job from removing the protection and it is off unless you ask for it — everything else about your document comes through untouched either way.

Also take out what the file remembers about where it came from

This opens once the document above has been opened. There is nothing on this document to remove. Show Hide There is no protection on this document. Nothing here has anything to remove — it opens, prints and copies already. This document is not locked shut. It opens for anybody, and what it carries is a set of restrictions that readers are asked to honour. No password is needed to take them off. This document needs a password to open. Nothing on this page can find one, so it has to be typed in below. Opened. The protection can come off now. RC4, {bits}-bit — revision {r} AES-{bits} — revision {r} The encryption on this file has been considered broken for years: a {bits}-bit RC4 key is short enough to be searched outright. RC4 is long superseded, though a 128-bit key is not something anyone searches by brute force. A modern cipher with a key derivation from 1994. AES itself is sound; the password behind it is hashed the old way, which makes guessing one far cheaper than the cipher suggests. AES-256 as Adobe first published it in 2008, and later withdrew: the password hash turned out to be cheap enough to attack at speed. The current scheme, and the only one here still considered strong. A document locked this way is as good as the password on it. No password. The document was never closed — only restricted. The password you typed, which is this document’s open password. The password you typed, which is this document’s owner password — the one that lifts its restrictions. The key was checked against the document’s own check value and matched. {size} · {pages} Readers of this document are asked to refuse the following: This document restricts nothing. Everything it protected was the password to open it. Printing it Changing anything on a page Copying text or pictures out of it Adding a comment or a highlight Filling in its form fields Reading it aloud to somebody who cannot see it Adding, deleting, rotating or reordering pages Printing it at full quality rather than as a coarse picture That is not the password for this document. Both the password that opens it and the owner password that lifts its restrictions are accepted here, and neither of those was it. This document is locked to a certificate rather than a password (/{name}). Opening it needs the private key it was issued to, which is held by whoever set it up and is not something a password box can stand in for. This document uses a version of PDF encryption this tool does not implement (V{v}, R{r}). Every published scheme is handled; this one is either an undocumented variant or newer than this page. This document says it is encrypted but its encryption dictionary is incomplete, so there is nothing here to work from. The file is damaged. That is not a PDF. This tool only works on PDF files. This PDF is encrypted. This file has no document catalogue, so there is nothing to unlock. It is either not a PDF or damaged past what can be repaired here. This does not start like a PDF: there is no %PDF- header. This PDF could not be read: {detail} a Flate stream would not decompress ({detail}) this browser has no CompressionStream an LZW stream starts with an undefined code this stream is encrypted an unknown filter, /{name} nested too deeply ran off the end unexpected {found} at {at} unexpected byte 0x{hex} at {at} a stream with no endstream no obj keyword at {at} no startxref not an xref section an xref stream with no /W an xref stream with zero-width fields This file’s cross-reference table did not match its contents, so it was read by scanning for objects instead. That is a repair, and it worked, but check the result before you send it anywhere. This document has been edited and re-saved at least once, so it is carrying older copies of objects that nothing points at any more. Those are left out of the file you get back. {n} bytes {n} KB {n} MB {n} page {n} pages Writing it back out without the encryption Opening it again to check Cancelled. Nothing was changed; press the button to start again. {size} — no password, no restrictions. Every page, every font and every picture is the one that arrived. What is gone is the encryption around them. Checked: {found} This run did not check out — {found}. Keep your original. opened again from memory with no password at all, and it is 1 page, the same as the original. opened again from memory with no password at all, and it is {pages} pages, the same as the original. the finished file came back with {pages} pages instead of {expected} the finished file still asks for a password, which means the encryption was not removed the finished file would not reopen ({detail}) {n} restrictions lifted. 1 restriction lifted. The document was decrypted with its own key and written back out with no encryption dictionary at all. What the file remembered about where it came from was removed as well. This document carried a digital signature. Rewriting a file breaks any signature on it, so the copy you get back is unsigned — the original is still the signed one. Older, superseded copies of objects from earlier edits were not copied over. The original’s cross-reference table was broken and had to be rebuilt by scanning. Check this file before sending it on. your document has gone nowhere. {total} files loaded, all of them this page's own. {platform} something contacted {hosts}, which this tool never does. Treat that as worth investigating. {platform} The page's own ad, measurement and donate-button scripts loaded from {hosts} host; not one of them was given a document or a byte of one. The page's own ad, measurement and donate-button scripts loaded from {hosts} hosts; not one of them was given a document or a byte of one.

# Unlock PDF — take off the password and the restrictions Most locked PDFs need no password at all. This one says which kind you have before it touches it. > Take the password and the printing, copying and editing restrictions off a PDF in your browser. Most protected files need no password at all, and this one tells you which kind you have. Nothing is uploaded, and it never guesses a password. 이 페이지는 브라우저 안에서만 동작하는 대화형 도구입니다(https://abox.tools/ko/unlock-pdf/). 도구에 넘긴 어떤 것도 업로드되지 않습니다. 아래는 이 페이지가 도구에 대해 글로 설명하는 내용 전부입니다. 도구를 쓰려면 이 주소를 여세요. ## documents **절대 업로드되지 않습니다**. 서버가 아예 없으니까요. The document you choose is opened, decrypted and written back out in memory on this machine, by code served from this address. Nothing here can make an upload, and there is no server on the other end of this page to receive one. Neither the file nor the password you type leaves the tab. - ✗ No upload - ✗ No account - ✓ Works offline - ✓ Open source - ✓ Files stay on your device ## How to remove a password or the restrictions from a PDF 1. **Choose the PDF.** One document at a time. It is read straight off your disk by the browser, and the first thing that happens is that it is tried with a blank password — which is what opens the majority of protected files, because the majority of them were never closed. 2. **Read what the page found.** It says which of the two kinds of protection this file has, what scheme was used and what that scheme is worth today, and lists every restriction the document asks readers to honour: printing, copying, editing, commenting, filling in forms, reordering pages, even reading it aloud to somebody who cannot see it. 3. **Type the password, but only if you are asked.** The box appears only when the blank password did not open the document, which is the only time a password is any use. Either of the document's two passwords works — the one that opens it, or the owner password that lifts its restrictions. Nothing is guessed, and what you type stays in this tab. 4. **Take it off, and read the line that says it was checked.** The document is decrypted with its own key and written back out with no encryption dictionary at all. Then the finished file is opened again here, with no password, by a reader that refuses encrypted documents — and if it will not open, or comes back with a different number of pages, you get no download and a message saying so. ## 자세한 설명 [How to unlock a PDF, and which kind of locked it is](https://abox.tools/ko/guides/unlock-a-pdf/): A PDF that will not print and a PDF that will not open are two different problems with one name. What each of them actually is, why one comes off in a click and the other cannot come off at all, and how to tell which you have. ## 자주 묻는 질문 ### Do I need the password? Usually not, and the page tells you within a second of choosing the file. Most "protected" PDFs — bank statements, payslips, exported reports, anything from an office suite's "restrict editing" box — open for anybody and merely carry a list of things readers are asked not to do. Those come off with one click and no password. A document that genuinely asks you for a password when you open it is the other kind, and for that one you need the password. ### Can it open a PDF whose password I do not have? No, and it does not try. There is no dictionary, no word list and no brute-force search anywhere in this tool — you can read `src/crypt.js` and see that there is no loop in it. For the oldest documents, with 40-bit keys, a search would in fact work, which is exactly why the refusal is written down rather than left to be assumed. If you have lost the password to your own document, this page cannot help you and neither can any honest one. ### What is the difference between the two passwords? A PDF has room for two. The *user* password is the one a reader asks you for; without it the file does not open. The *owner* password lifts the restrictions — printing, copying, editing — and a document very often has an owner password with no user password at all, which is why it opens for everybody and still refuses to print. This tool accepts either one, and tells you which of them the document actually let it in with. ### Is removing the restrictions legal? That depends on the document and on where you are, and it is a question about your rights in the file rather than about the technology. What can be said plainly is what the format does: the restrictions are a field inside the document that readers honour by agreement, not a cryptographic barrier, and Adobe has documented them that way since they were introduced. This tool is for documents you are entitled to use — your own statement that will not print, a report you paid for that will not copy, a scan you need to reorder. If you are not entitled to the file, nothing here changes that. ### Which kinds of encryption does it handle? Every published one: RC4 at 40 and 128 bits (revisions 2 and 3), AES-128 (revision 4), and AES-256 in both the withdrawn 2008 form and the current PDF 2.0 one (revisions 5 and 6). What it does not handle is certificate-based encryption, where the key belongs to a smart card or a key store rather than to a password, and Adobe's one unpublished variant. Both are refused with a message saying which they are, rather than failing vaguely. ### Will the document look any different afterwards? No. Nothing is re-rendered, re-encoded or reflowed: every page's drawing instructions, every embedded font and every image is copied through exactly as it arrived. Text stays selectable, scans stay at their original resolution, and nothing moves. The file may come out slightly smaller, because a rewrite leaves behind the superseded copies of objects that earlier edits left in it. ### What happens to a signed document? Its signature stops being valid, and there is no way round that. A signature covers the exact bytes of the file it was applied to, so any change at all — by any program, including the one that signed it — invalidates it. That is the whole point of a signature. This tool writes a new file, notices when the original was signed, and says so on the results. Keep your original: it is still the signed one. ### Are my documents or passwords uploaded anywhere? No. The file is read, decrypted and written by your own browser on your own hardware, and the password goes into a key derivation running in this tab. There is no server side to this tool, and the page's `Content-Security-Policy` names every address it may contact — none of them belongs to this site. The simplest way to satisfy yourself is to unplug from the network and use the page anyway. ### How do I know the protection is really gone? Because the tool checks, on your machine, and shows you the result. When the file has been written it is handed back to the same reader that the other PDF tools on this site use — one that refuses an encrypted document outright — and it has to open with no password and come back with the same number of pages. If it does not, the run is reported as failed and nothing is offered for download. You can check it yourself afterwards too: open it in any reader and look at the document properties, where every permission should now read Allowed. ### Is there a size limit, and does it cost anything? There is no limit written into the tool. The limit is your own machine: the document is held in memory while it is worked on, so a laptop will take a few hundred megabytes without complaint and will struggle somewhere above that. It is free, there is no account, no sign-in and no trial. The site carries advertising, which is what pays for it; the ads are not given anything about your documents. ### Does it work offline? Yes. Load the page once, then disconnect from the internet and it keeps working. That is also the simplest way to prove nothing is being uploaded: a tool that sent your document away to be unlocked would stop the moment you unplugged. ## 이 약속을 직접 확인하는 방법 - **Most protected PDFs are not locked at all, and this page says so before it does anything.** A PDF can carry two quite different things. An *open password* is real: without it the file cannot be read, and nothing here will find one. *Restrictions* — no printing, no copying, no editing — are not. A file carrying only those opens for anybody, which means it has to contain everything needed to derive its own key, because your reader derived it. What stops the reader printing is a permissions field inside the document, honoured by agreement between well-behaved programs. Adobe documented that from the beginning. Removing it is not breaking anything; it is declining to volunteer. The page tells you which of the two you have, and only asks for a password when there is genuinely one to ask for. - **It does not guess passwords, and there is no loop in it that could.** If a document has an open password, you supply it or the document stays shut. There is no dictionary here, no word list, and no attempt on the 40-bit keys of the 1990s that really would fall to a search. That is a deliberate line rather than a limitation nobody got round to: a page that quietly tried a few million passwords for you would be a different tool with a different name, and it is not this one. Both the password that opens a document and the owner password that lifts its restrictions are accepted, because either one is a password you were given. - **The password is typed here and used here.** What you type goes into a key derivation running in this tab and nowhere else. It is not stored, not remembered between files, and not written to the address bar, and the page's `Content-Security-Policy` names every address this page may contact — not one of them belongs to this site. A tool that asked for a document password and then made a network request would be doing the single worst thing a tool of this kind can do. - **The finished file is opened again, here, before you are offered it.** Everything above is this tool marking its own homework until that happens. So the bytes that are about to become your download are handed to the same reader that [the compressor](https://abox.tools/ko/pdf-용량-줄이기/), [the merger](https://abox.tools/ko/pdf-합치기/) and [the redactor](https://abox.tools/ko/pdf-가리기/) use — a reader that refuses an encrypted document outright — and it has to open with no password and come back with the same number of pages. A file that still had any encryption on it could not pass that. If it does not, the run is reported as failed and there is no download. - **The pages themselves are not re-rendered, re-encoded or reflowed.** What changes is the encryption around the document, not the document. Every page's drawing instructions, every embedded font and every picture is written back out exactly as it arrived, so text stays selectable and searchable, scans stay at the resolution they were scanned at, and nothing shifts on a page. The one thing that does change is what a rewrite always changes: older superseded copies of objects left behind by earlier edits are not carried over, which usually makes the file a little smaller. - **A digital signature cannot survive this, and the page says when there is one.** A signature covers the exact bytes of the file it was applied to, so any rewrite invalidates it — that is what a signature is for. This tool writes a new file, so the copy you get back is unsigned, and it says so on the results when it finds a signature to warn about. Your original is still the signed one. There is no way round this and no tool that has one. - **It says what the protection was actually worth.** A document locked with 40-bit RC4 in 1998 and one locked with AES-256 last year both say "password protected" in a reader, and they are decades apart. The page names the scheme, the key length and the revision, and says plainly which of them are broken, which are merely superseded, and which is current. That is worth knowing about a file you were told was secure, and no reader shows it to you. - **Certificate-locked documents are turned away rather than half-opened.** Some documents are encrypted to a certificate rather than a password — the corporate kind, where the key lives in a smart card or a key store. Those are refused with a message saying what they are. Nothing typed into a password box can stand in for a private key, and pretending otherwise would waste your time. - **What Google loads, and what it is not given.** The ad and measurement scripts come from Google. Neither is handed anything about your document: not a file, not a page, not a name, a size, a page count, a password, or what the file was protected with. Every line that reads, decrypts or writes a PDF is served from this origin and listed in the repository. - **What the donate button loads, and what it is not given.** The "Buy me a coffee" button in the header is drawn by a script from cdnjs.buymeacoffee.com and letters itself from Google Fonts. It is a link and nothing more: it reports no visit, and it is handed nothing about you or your documents. Nothing happens unless you click it, and what you would be clicking through to is somebody else's site. - **It works offline.** Disconnect from the network and everything on this page still functions. That is the simplest proof of all: a tool that sent your document away to be unlocked would stop. **직접 확인해 보세요.** 위에 적은 어느 것도 그냥 믿으실 필요는 없습니다. 이 페이지는 저장소 안의 템플릿과 설정을 빌드 스크립트가 찍어 낸 결과이고, 그 스크립트는 누구나 읽고 직접 돌려 볼 수 있습니다. 결과물은 `dist` 브랜치에 그대로 올라가 있고요. 그래서 실제로 제공되는 파일과 소스를 빌드한 결과를 나란히 놓고 비교해 보실 수 있습니다: https://github.com/A-Box-of-Tools/website 먼저 읽어 볼 파일을 꼽자면, Content-Security-Policy는 `config/site.toml`, `src/crypt.js` for how a password becomes a document's key — and for the fact that there is no loop in it anywhere — and `src/aes.js` and `src/rc4.js` for the two ciphers themselves. None of them can reach the network, and neither can the reader or the writer beside them.

자주 묻는 질문

Do I need the password?

Usually not, and the page tells you within a second of choosing the file. Most "protected" PDFs — bank statements, payslips, exported reports, anything from an office suite's "restrict editing" box — open for anybody and merely carry a list of things readers are asked not to do. Those come off with one click and no password. A document that genuinely asks you for a password when you open it is the other kind, and for that one you need the password.

Can it open a PDF whose password I do not have?

No, and it does not try. There is no dictionary, no word list and no brute-force search anywhere in this tool — you can read src/crypt.js and see that there is no loop in it. For the oldest documents, with 40-bit keys, a search would in fact work, which is exactly why the refusal is written down rather than left to be assumed. If you have lost the password to your own document, this page cannot help you and neither can any honest one.

What is the difference between the two passwords?

A PDF has room for two. The user password is the one a reader asks you for; without it the file does not open. The owner password lifts the restrictions — printing, copying, editing — and a document very often has an owner password with no user password at all, which is why it opens for everybody and still refuses to print. This tool accepts either one, and tells you which of them the document actually let it in with.

Is removing the restrictions legal?

That depends on the document and on where you are, and it is a question about your rights in the file rather than about the technology. What can be said plainly is what the format does: the restrictions are a field inside the document that readers honour by agreement, not a cryptographic barrier, and Adobe has documented them that way since they were introduced. This tool is for documents you are entitled to use — your own statement that will not print, a report you paid for that will not copy, a scan you need to reorder. If you are not entitled to the file, nothing here changes that.

Which kinds of encryption does it handle?

Every published one: RC4 at 40 and 128 bits (revisions 2 and 3), AES-128 (revision 4), and AES-256 in both the withdrawn 2008 form and the current PDF 2.0 one (revisions 5 and 6). What it does not handle is certificate-based encryption, where the key belongs to a smart card or a key store rather than to a password, and Adobe's one unpublished variant. Both are refused with a message saying which they are, rather than failing vaguely.

Will the document look any different afterwards?

No. Nothing is re-rendered, re-encoded or reflowed: every page's drawing instructions, every embedded font and every image is copied through exactly as it arrived. Text stays selectable, scans stay at their original resolution, and nothing moves. The file may come out slightly smaller, because a rewrite leaves behind the superseded copies of objects that earlier edits left in it.

What happens to a signed document?

Its signature stops being valid, and there is no way round that. A signature covers the exact bytes of the file it was applied to, so any change at all — by any program, including the one that signed it — invalidates it. That is the whole point of a signature. This tool writes a new file, notices when the original was signed, and says so on the results. Keep your original: it is still the signed one.

Are my documents or passwords uploaded anywhere?

No. The file is read, decrypted and written by your own browser on your own hardware, and the password goes into a key derivation running in this tab. There is no server side to this tool, and the page's Content-Security-Policy names every address it may contact — none of them belongs to this site. The simplest way to satisfy yourself is to unplug from the network and use the page anyway.

How do I know the protection is really gone?

Because the tool checks, on your machine, and shows you the result. When the file has been written it is handed back to the same reader that the other PDF tools on this site use — one that refuses an encrypted document outright — and it has to open with no password and come back with the same number of pages. If it does not, the run is reported as failed and nothing is offered for download. You can check it yourself afterwards too: open it in any reader and look at the document properties, where every permission should now read Allowed.

Is there a size limit, and does it cost anything?

There is no limit written into the tool. The limit is your own machine: the document is held in memory while it is worked on, so a laptop will take a few hundred megabytes without complaint and will struggle somewhere above that. It is free, there is no account, no sign-in and no trial. The site carries advertising, which is what pays for it; the ads are not given anything about your documents.

Does it work offline?

Yes. Load the page once, then disconnect from the internet and it keeps working. That is also the simplest way to prove nothing is being uploaded: a tool that sent your document away to be unlocked would stop the moment you unplugged.