I've come up with a temporary and MESSY, UNSUPPORTED work around for those of you brave enough to try it. I've tested it myself a few times and it seems pretty legit, so here's a hack you can use until official attachment support is released: WHAT YOU NEED A real computer (Windows 10, MacOS or Linux); this method will not work on phones because they're so stripped down as to not include the necessary software in a way you can access it. If on Windows 10, you'll need the Windows Subsystem for Linux installed and ready. MacOS and Linux already ship with the necessary tools. WARNINGS / CAVEATS Can't access attachments on your mobile device; again, because mobile OS's are so stripped down and powerless it's not even funny. Small files only! I can't stress this enough. If your file is over a few megabytes in size, while that might work for a few cases here and there, over time it's going to make for one hell of a messy database that Enpass has to wrangle, thus making it slow and possibly unstable (and where there's instability, there's the possibility for data loss). Do not, I repeat DO NOT go putting your damn wedding photos up here, ya'll. Think plain-text or no-image PDFs of a few kiloybtes as receipts for stuff. That's it. Nothing more because, again this is a hack, not an officially-supported feature. OKOKOK HOW DO I DO THE THING? This example is taken from MacOS 10.12 so you may need to adjust the command name, path and/or args depending on your platform if they differ. The basic idea: Take that file you've got in its present, binary mode; Run it through a base64 encode operation. This takes the binary data and transforms it into a series of "jibberish" text strings that in fact, actually mean something. It's basically a way to translate the "ones and zeros" into a copy-pastable format. Copy and paste that output into Enpass's notes field for your item of choice along with some remarks on what it is that's in there and how to restore it later. Step 1: Encode the data Given the file $HOME/Downloads/something.zip, which is presently in binary format, I'll change that into plain-text format with the following command: base64 -b 80 -i $HOME/Downloads/something.zip > $HOME/Downloads/something-base64-encoded.txt What do these options mean? Well, -b 80 means "insert a new line every 80 characters". This is more for presentation and ease-of-visibility on your part and can be ommitted if absolutely necessary. The -i option tells it which input file to look at. I...input...you get ;-) The argument following -i is, naturally, the file we have - binary. Next is the greater-than symbol >. This is a shell output redirection thing - it basically says "hey, all that crap on the left? yeah shove it into this thing on the right". Said thing on the right is the path to a file that doesn't yet exist when we run this, thus it will CREATE that file on the fly. Step 2: Copy-Pasta This is obvious and wicked easy. Open that file in a text editor or for the more console-inclined like myself, run cat $HOME/Downloads/something-base64-encoded.txt | pbcopy. On MacOS, "pbcopy" is "paste buffer copy" which means "copy it" as if you hit CMD+C. On Linux you can use "xsel" if it's installed. Windows users, I don't know what to tell you other than "use the mouse and notepad.txt" =) Open Enpass, find your item of choice, scroll to the notes field (or create a new huge plain text body field) and paste it in there. Step 3: Write Down How to Put It Back Together! The point of this entire exercise is to be able to re-assemble this file at a later date with another simple copy-paste. Naturally, that could be years from now and you may not be able to find this post, so dammit, make a note! ;-) At the top of the text entry field, write what the attachment's original filename was and what it's for, bumping the base64 encoded binary payload (the "jibberish text") down a few lines while you're at it, and then before saving, enter this as instructions on how to put it back together: Given you've copied the base64 payload only from that field and pasted it into a file named $HOME/Desktop/backup.txt: base64 -D -i $HOME/Desktop/backup.txt -o $HOME/Desktop/original-filename.whatever The arguments listed: -D Capital "Dee" says decode the data. To "decode" here means "you gave me plain text letters, I want binary dammit so imma make that binary by DECODING the plain text". -i is, as before, the input file. Note that you do indeed need this to exist before you run this command. -o is where to put the output file. Note that this doesn't need to exist (it'll be created on the fly), but you do need to tell it the exact, full filename that it should have so that things work with it properly. If you compressed a PDF file (receipt.pdf), make damn sure you restore it as anything ending in ".pdf". If you don't, or maybe you leave off ".zip" for a zip file, or ".jpg" for an image, you may not be able to use the file in the future. Now that you've written that stuff in there and pasted the base64 encoded payload, SAVE YOUR WORK. Now, SYNC YOUR WORK. It would also be a good idea to move to another computer and try to restore from it given your restoration instructions as well, just in case. More info: man base64 -- Apple's best existing (?) copy of a manual page on the base64 utility. MacOS users may need to install developer tools (xcode-select --install in terminal) before they have this command available. For Linux and Windows Subsystem for Linux (which is...as the name implies, Linux...) use your package manager and search for it, then install the appropriate package to gain access to the command. Warning/Tip Newer users might be tempted to visit a website to do this Base64 encode/decode process for them. DON'T DO IT. You have no way to guarantee that everything you paste into your web browser form isn't being copied up to "who-knows-where", meaning that your attachment is now in the hands of "who-knows-whom". Best to use the command line tools instead and keep it all on your local machine to prevent accidental leakage of private details.