Files.com lets you tag any file or folder with your own metadata — customer IDs, claim numbers, compliance classifications, workflow status — then search, filter, automate, and govern on it. Metadata Categories turn that into a reusable, enforced schema, so the same kind of file is classified the same way everywhere it lives — including on the S3, Azure, and on-prem storage you mount but don’t host.
Every file platform knows a file by its name, its size, and where it sits. That’s fine until a working folder fills up with thousands of files from dozens of partners, and “find the one for claim 88421” turns into scrolling and guessing. Renaming everything to encode the detail you need is the usual workaround, and it breaks the first time a partner names a file their own way.
Custom Metadata lets you attach the business meaning of a file directly to the file — the customer it belongs to, its approval status, the compliance class it falls under — so you find, sort, and act on files by what they actually are, not by a naming rule nobody follows the same way twice.
Once a file carries its own metadata, the rest of the platform can act on that meaning the same way it acts on a name or a date.
Search metadata values right in the web app, or add a metadata key as a column and filter a folder by it. Look up a file by customer ID, claim number, or invoice number in one step — so “where’s the file for order 5567” is a search, not a scroll through a thousand files.
Metadata Categories are reusable schemas — a named set of keys, each free-form or restricted to a fixed list of allowed values. Assign one to a folder and every file in it uses the same keys and values, so classification stays consistent instead of drifting into forty spellings of the same thing.
A metadata value can trigger an automation or decide where a file goes next. Route by the department recorded on the file, expire records by their retention class — rules you set once, not scripts you keep alive.
Tag files with the compliance class they fall under — HIPAA, GDPR, PCI — and that classification travels with the file into the audit record. An auditor’s “show me every record in scope” becomes a filter, not a project.
A Metadata Category is a template you build once: the keys that matter for a kind of file, and for each key either free-form text or a fixed list of allowed values. Assign the Category to a folder and it applies to every file and subfolder underneath, so the same invoice fields, the same case fields, the same media attributes show up wherever that kind of file lands.
When someone enters a value outside the allowed list, or a key the schema doesn’t recognize, Files.com flags it for review instead of silently changing or dropping it — and assigning a Category never overwrites the metadata already on your files. You get enforced consistency without losing anything you previously recorded.
Custom Metadata is the same system whether you set values by hand, pick them from a Category, or let File Extraction read them straight out of an inbound XML, JSON, or EDI file. Extraction fills the fields automatically, Categories keep them consistent, and search and automation act on them. It’s one classification layer, not four disconnected features.
And it isn’t limited to files stored on Files.com. Files and folders on Remote Server Mounts — your own S3, Azure Blob, SharePoint, or on-prem NAS — carry the same Custom Metadata and priority colors, so you classify and prioritize files across every backend you run from one place.
What teams ask about tagging files, building reusable Metadata Categories, searching by business value, and where the metadata lives.
Start a free trial, build a Metadata Category for the files you handle most, and turn business meaning into something you can search, filter, automate, and audit on — anywhere your files live.
No credit card required • Free for 7 days • Live in minutes