Public Hosting (Web Hosting)

Public Hosting transforms your Files.com site into a secure, globally accessible web server for files and static content. Organizations use Public Hosting to distribute software downloads, documentation, media assets, forms, training materials, and other resources through simple HTTPS URLs, without requiring visitors to install software, use a specific protocol, or create a Files.com account.

Whether you’re publishing public documentation, delivering software updates, sharing marketing assets, or serving customer resources, Public Hosting provides a fast and reliable way to make content available on the web while keeping it under the same governance and storage controls as the rest of your Files.com environment.

Each Publicly Served Folder can be open to anyone with the URL, restricted with a password, or gated behind your Files.com site login. Folders are configured independently, so a single site can mix open, password-protected, and login-required folders simultaneously. Public Hosting serves over HTTPS by default and can use a branded Custom Domain in place of the default hosted-by-files.com address, with no edge platform required. Edge platforms are there for cases that need more control, such as rewrite rules that route across multiple domains or regions.

Permission Fences

Public Hosting has a Combine nested effect, so a subfolder cannot turn off inherited Public Hosting with the explicit-disable option. Adding a separate Public Hosting configuration at the subfolder also leaves the parent's URL available for that content.

A permission fence blocks Public Hosting inherited from a parent folder. The fenced folder and its contents are omitted from the parent's public directory listings and are not served when requested through the parent's Public Hosting URL. To publicly host content inside the fenced subtree, configure Public Hosting at the fence boundary. This is the same boundary enforced for a Share Link created above a permission fence.

Common Use Cases

The use cases below illustrate how customers put Public Hosting to work.

Software and Technology

Software companies use Public Hosting to distribute files to a variety of audiences.

Distribute software files, updates, and patches with version-controlled URL systems where endpoints like /latest/ redirect to the current version, so users always access the most recent build. Files.com itself uses Public Hosting to publish updates to some of our client apps.

Development teams serve API documentation, SDKs, and code samples publicly, giving developers direct HTTPS access to those resources.

Internal Tools and Dashboards

Teams use Public Hosting to serve internal runbooks, status dashboards, training materials, and team portals. When the folder is configured to require site login, only users already registered on your Files.com site can reach the content, making it practical for internal audiences without exposing anything to the open internet. AI tools connected to Files.com via the MCP server can generate and publish dashboards or reports directly to a hosted folder, making them live for the team instantly. See Public Hosting Use Cases for details on internal and external hosting patterns.

Healthcare and Professional Services

Healthcare providers share intake forms, educational materials, and appointment preparation guides through clean, memorable URLs.

Legal firms publish standard contracts, disclosure forms, and regulatory documents so clients can retrieve paperwork directly.

Professional training organizations distribute certification materials, course content, and compliance training resources, giving learners reliable access without a login system.

Marketing and Media

Marketing departments share press kits that give media outlets direct access to high-resolution images, logos, and promotional materials. Companies run centralized brand asset distribution systems that provide partners and vendors with consistent branding materials.

Simple promotional sites or product showcases that don't require interactivity work well on Public Hosting. Digital catalogs containing product information, price sheets, or specification documents can be shared with prospects and partners directly.

Event Management

Event organizers use Public Hosting to reduce the complexity of event participation.

Create resource hubs that share speaker biographies, presentation slides, and event schedules with attendees before, during, and after events.

Simplify registration by providing direct access to event forms, venue maps, and attendee information.

E-commerce and Retail

Host product manuals, warranty information, and troubleshooting resources so customers can find answers without contacting support.

Share product data feeds with partners or marketplace platforms to automate inventory synchronization.

Provide direct access to return and exchange forms to reduce friction in customer service workflows.

International and Localization

Global companies serve localized manuals, compliance documents, and region-specific content using edge routing, so users automatically receive materials for their location.

Distribute marketing materials adapted for different markets, keeping messaging consistent while respecting local preferences and regulations.

File Types and Web Applications

Public Hosting serves any file type and MIME type, including HTML, XML, CSS, JavaScript, images, videos, audio files, PDFs, and text files.

You can host a working web application in a Publicly Served Folder, not just static files. Because JavaScript runs in the visitor's browser, an app can fetch live data from any external API and render it dynamically without any server-side code on Files.com. This approach is called JamStack.

Enable HTML sandboxing when publishing HTML from people who should not be able to run scripts on your hosting domain. Sandboxed HTML cannot run a web application that requires JavaScript.

Public Hosting does not run server-side code. PHP, .NET, and JSP are not supported.

Public Hosting Domain

Public Hosting uses [subdomain].hosted-by-files.com separately from your site's primary domain. This keeps hosted content outside the browser origin used by your Files.com web interface and API, so it does not inherit authenticated access to that application.

Hosted folders on the same domain share a browser origin, even when they have different URLs or passwords. A page that runs scripts can read another hosted folder when the visitor's browser supplies the access required for that folder. Choose who can publish accordingly, or use HTML sandboxing or a folder served only on its own custom domain. Public Hosting explains these controls and their scope.