Using Edge Platforms with Public Hosting

Public Hosting lets you share files and directories via public URLs. By default, those URLs are served under the hosted-by-files.com domain.

To serve Publicly Hosted Folders from your own domain, put an edge platform in front of your Files.com public links. Cloudflare Workers, Netlify Edge Functions, Akamai EdgeWorkers, Vercel, Fastly Compute@Edge, and AWS Lambda@Edge all support URL rewriting at the edge. Each provider lets you modify requests and responses without redirecting users or exposing the underlying Files.com URLs. Refer to Implementing URL Rewrites for setup instructions.

This pattern gives you full control over the domain, branding, and delivery experience without requiring integration work on the Files.com side.

Caching at the edge also reduces repeat requests to your Files.com site. Users download content from the edge platform's servers instead of going back to Files.com on every request, which lowers outbound data usage and reduces transfer usage costs.

For example, when you distribute large files such as product manuals, videos, or software installers, only the first request reaches Files.com. Subsequent downloads are served from the edge. The savings are meaningful at scale.

Customers use this pattern to serve assets under multiple brands from one source, hide folder structure or version numbers behind clean URLs, present trusted custom domains to patients in healthcare, deliver branded promotional assets in media and entertainment, and route region-specific technical documentation in manufacturing and distribution. See Edge Platforms with Public Hosting Use Cases for examples of each.