Декодируйте Base64 в PDF
Tool guide
Accounting APIs, banking back-ends and document-exchange systems often return an invoice or a signed act as a long Base64 string inside JSON rather than as a file. This page turns that string back into a PDF and renders it in an inline preview, so you can read the document before it touches your disk, then save it with the download button. Decoding happens inside the tab, so the paperwork is not relayed through anyone's server. See also: get a Base64 string out of a file again, save Base64 as a file of any type, split the resulting PDF into page images.
Check how the string starts. A real PDF begins with the %PDF signature, which in Base64 looks like JVBERi. A different opening means the payload is not a PDF at all. The other common cause is a truncated copy from a console, where long values are shortened with an ellipsis — take the value from the raw response instead.
Invoices of a few hundred kilobytes open instantly. Multi-page scans of tens of megabytes are heavy: the string is about a third bigger than the file, and the text, the decoded bytes and the rendered preview all sit in the tab at once. If it stalls, download the file and open it in a desktop reader.
Decoding does not remove protection — you get back exactly the same encrypted document. The preview hands the file to the browser's built-in viewer, which will prompt for the password if it supports doing so. Printing and copying restrictions baked into the document survive unchanged.
No. The string is decoded by the page's own script, and both the preview and the download are served from a temporary object that exists only in your tab. Nothing is transmitted, so contracts and payment documents can be opened without publishing them to an outside service.
The same one the page is open in. On the English version the field reads Base64 Input and the buttons read Decode and Download PDF; the Russian version labels the very same controls in Russian. The tool's interface used to be English regardless of the site language, which is why older write-ups quote English captions. The steps above use exactly the captions you will see on screen.
Use the File to Base64 page for the opposite direction: choose the PDF in the file picker and you get the string to embed in JSON or an email body. The pair is handy when debugging an integration and you need to compare the string sent against the string received.
Before: {"docType": "invoice", "file": "JVBERi0xLjQKJcfsj6IKNSAwIG9iago8PC9MZW5ndGggNiAwIFI..."} After: A two-page invoice in the preview pane and a saved copy in downloads
Before: data:application/pdf;base64,JVBERi0xLjcKJeLjz9MKMSAwIG9iago8PC9UeXBlL0NhdGFsb2c...
After: A single-page receipt opening in the browser's built-in viewer
Your rating and feedback help decide what to improve next.