APIs and database columns frequently return PDFs as Base64 text, because it survives JSON transport safely. That leaves you holding a wall of characters when what you need is the document. This decodes the string back into a real PDF you can open and save.
Almost always a truncated string. Base64 PDFs are long and copying from a terminal or a log viewer often clips the end. Confirm the string finishes cleanly, with padding equals signs if present, and that no line breaks were introduced mid-copy.
No, which is the main reason to use a local tool for this. Base64 PDFs are commonly invoices, contracts and statements. The decode happens in your browser and the file never leaves your device.
Practically, your browser memory. A Base64 string is a third larger than the file it represents, so very large documents can be slow to paste and decode.
Base64-encoded PDFs almost always begin with JVBERi0, which is what the PDF header bytes encode to. If your string starts with something else it is probably a different file type, and the Base64 to Image tool may be the one you want.