Pick the large file.
Open the Encrypt flow and select the file. You do not need to split it, compress it, or move it anywhere first. Size is not a special case in AgePony 3.1.
There is no special procedure. AgePony 3.1 streams the file in chunks with bounded memory, so nothing is held in RAM and a 1 GB video behaves like a 10 KB note. It just takes longer, and you get a progress bar for that.
Open the Encrypt flow and select the file. You do not need to split it, compress it, or move it anywhere first. Size is not a special case in AgePony 3.1.
Add one or more recipient public keys (age or SSH), or switch to passphrase mode. This is the same recipient picker as any other file.
AgePony reads and encrypts the file in chunks and writes as it goes, which is why memory use stays flat instead of climbing with file size. The progress bar tracks real work, so on a big file it is worth leaving the screen open until it finishes.
You get a normal .age file. Send it, upload it, or keep it. Any standard age implementation reads it, whatever size it is.
If you are using a passphrase rather than a recipient key, AgePony 3.1 lets you adjust the scrypt work factor in Settings. A higher work factor makes a stolen file much harder to attack by guessing passphrases, at the cost of more time and more memory every time you encrypt or decrypt. On a device with less memory to spare, lowering it keeps large-file work comfortable. Raise it when the file matters more than the wait.
Decrypting, signing and verifying stream the same way. Large files behave consistently across all four operations, not just encryption.
Nothing imposed by AgePony. Since 3.1 the file is streamed in chunks with bounded memory, so the practical limit is free space on your device.
No. AgePony 3.1 introduced bounded-memory streaming, so memory use stays flat whether the file is 1 MB or 1 GB.
It controls how hard a passphrase is to guess by brute force. A higher work factor costs more time and memory on every encrypt and decrypt but resists guessing better. It is adjustable in Settings, which helps on devices with less memory to spare.
Yes. Decrypting, signing and verifying use the same streaming path, so large files behave the same way in those flows.
Free file encryption for iOS and Android. No accounts, no tracking, no servers.