File Content Preservation

Files.com preserves the content you upload. Storing or sharing a file does not strip its embedded metadata, remove scripts, or rewrite its contents. This lets you exchange the original file faithfully, including information that the receiving application needs.

Embedded Metadata Stays With the File

Image EXIF data, document properties, and other information embedded in a file remain part of that file. A recipient who downloads the original receives that information too, even when it is not visible in an ordinary preview. For example, a photograph can retain the location and camera information saved by the device that created it.

Prepare the file before sharing it if recipients should not receive some of its contents or metadata. Files.com permissions control who can access a file; they do not remove selected information from the copy delivered to an authorized recipient.

Changes You Request

Preserving an upload is separate from processing you explicitly configure. Features such as GPG encryption or decryption, document editing, and content transformations change files as part of the requested workflow. FTP's ASCII transfer mode can also convert line endings; Binary mode preserves the transferred contents.

These are deliberate processing choices. Uploading a file by itself is not a request to clean, redact, or modify its contents.

Previews and Published Content

A preview can show a converted or watermarked copy while the stored original stays intact. A PDF preview watermark does not remove metadata or hidden content. Review the file that recipients will actually receive when deciding what to share.

Public Hosting serves uploaded web content, including HTML and JavaScript. When scripts are enabled, running the publisher's script is an intended part of hosting that content. Hosting access, browser-origin separation, and HTML sandboxing control how the published content is used; they do not turn storage into a content-rewriting service.