The problem with “upload and share”
Most platforms that let you upload images or videos do something to them before anyone else sees them. They re-encode video to a fixed bitrate, strip EXIF data, compress images to save storage, or transcode to a delivery format that suits their infrastructure. The result lands on the recipient’s screen looking slightly worse than what you sent.
This is a deliberate trade-off on their end: it reduces storage and bandwidth costs. For a casual social post it might be invisible. For anything where quality matters, like a design handoff, a video clip for review, or a photo from a shoot, it is a real problem.
What FileGoat does
Nothing.
The file you upload is the file that gets stored. When someone opens the link and downloads it, they get a byte-for-byte identical copy of the original. FileGoat does not re-encode video, does not re-compress images, does not strip metadata, does not change the container format.
A 4K video stays 4K. A RAW photo stays a RAW photo. A lossless FLAC stays lossless.
How it works
Files go directly from your browser to object storage over an encrypted connection. The stored object is the original file. The download link points directly to that object. There is no processing step in between.
FileGoat does generate previews in the browser. Images are displayed inline and videos are playable, but these are rendered by your browser from the original file. No separate preview copy is created or stored.
Why this matters
If you are sending files to someone who will use them, a client, a colleague, or a collaborator, they should receive what you made, not a degraded approximation of it. FileGoat is a transfer tool, not a hosting platform, and it behaves accordingly.
The 5 GB limit exists because of infrastructure constraints, not because files are being transcoded down to a smaller size. What goes in is what comes out.