Metadata and Search, Built for How Teams Actually File Things

Describe the File. Let the Platform Handle the Rest.

Pydio Cells solves this by making the file's own description do the work a folder path used to do. Tag a document with what it is — client, project stage, document type, whatever your team actually tracks — and it becomes findable by that description from anywhere in the workspace, regardless of which folder it happens to sit in.

Built-In File Tagging & Discovery Toolkit

A few of the ways Cells helps teams stop relying on folder memory:

• Metadata fields your team defines, not a fixed schema: Cells v5 lets any team set up its own custom fields — client name, project phase, status, whatever categories actually matter to that group's work.
• Tag as you go, not in a separate step: Fields appear inline on the file itself, so tagging happens at upload or any time after, without opening a separate cataloguing tool.
• Type-ahead search across tags and content: Start typing and matching files surface immediately, searched against their tags, filenames, and file content together — not filenames alone.
• One discussion thread per file or folder: Comments and chat live directly on the item they're about, so the reasoning behind a tag or a decision doesn't end up in a separate email thread.
• Annotate images and video directly: Mark up a frame or a region on visual assets in place, instead of describing "the thing in the top left" over chat.
• Field order and search-eligibility, your call: Choose which fields actually show up in results and in what order, so search stays relevant instead of noisy.
• Automatic tagging on upload: Pair with Cells Flows to apply a starting tag automatically when a file lands in a given Cell, so nothing enters untagged and unfindable.
• Search reaches into Pages, too: The same search that finds a tagged file also surfaces relevant Pages content, so a written runbook and the files it references turn up together.

Getting From "Where Is It" to "Found It"

• Set up a handful of fields that match how your team actually describes its own work, not a schema imposed from outside.
• Tag files as they're created or uploaded, either by hand or automatically through a Flow.
• Search by typing what the file is about; matches come from tags, filenames, and file content together.
• Discuss the file where it lives, so the next person who searches for it finds the context along with the document.