Limitations

The Files.com S3-compatible endpoint handles certain S3 operations differently from Amazon S3 and other object-storage systems. The differences come from the Files.com filesystem model and keep S3 access consistent with the rest of the platform.

No Recursive Listings

The Files.com S3-compatible endpoint does not perform recursive listings. A ListObjects or ListObjectsV2 request returns only the items directly inside the targeted folder. Files inside subfolders, or in any deeper nested path, do not appear in the listing unless the client issues additional listing requests for those specific paths.

Many S3 clients automatically perform recursive listings by requesting a prefix with Delimiter=/. Files.com always returns a non-recursive listing, and clients must explicitly list each folder they want to explore.

Prefix Behavior

The S3 prefix parameter filters results within the targeted folder but does not cause Files.com to traverse subfolders. A prefix such as reports/2024/ returns only the contents of that folder. Subfolders require separate listing calls, even when a prefix matches a deeper path.

Some S3 clients assume that listing a prefix automatically returns all nested objects. When a client expects recursive behavior, it may appear to "miss" files or display incomplete results. To get full visibility, configure the client to list folders individually rather than relying on a single recursive listing.

Directory Semantics

Amazon S3 treats folders as logical prefixes, but Files.com maintains a true directory structure. The S3 protocol does not natively express this distinction, so Files.com returns listings that reflect the actual directory layout. Clients that depend on object-storage behaviors, such as inferring empty directories from key names, need to use standard folder listings for accuracy.