Find and manage
The shortest route to a file should be the obvious one. FileYard keeps a familiar folder model while adding tools that help a large library stay usable.
- Browse files and folders across separate spaces.
- Search by name and metadata without manually walking the directory tree.
- Preview supported documents and media before downloading.
- Upload, rename, move, copy, and delete from the web interface.
- Use recent-file views to return to active work quickly.
Ordinary files underneath
FileYard’s central design choice is also its simplest: local storage remains a normal directory tree. The server adds management and access; it does not turn every file into a proprietary database record.
That means your existing backup software, shell tools, and filesystem utilities can still work with your data. Stop FileYard and the files remain readable where you placed them.
Share and control
Share access without handing over the rest of the library. Links can be scoped to the selected file or folder and managed after they are created.
- Create direct links for files and folders.
- Add a password when the contents need another boundary.
- Set an expiration date for temporary access.
- Choose whether recipients can download.
- Revoke a link without moving or renaming the underlying file.
- Review relevant activity through audit logs.
Permissions apply to normal user access too, so a household, team, or lab does not have to treat every account as an administrator.
Connect your devices
The web interface is only one gate into the yard.
| Access path | Intended use | Current note |
|---|---|---|
| Responsive web | Browsing, management, search, and sharing | Core experience |
| Desktop sync | Folder sync on Windows, macOS, and Linux | Windows client is in alpha; hardware coverage is still growing |
| Android | Mobile access and file actions | Emulator tested; physical-device validation remains |
| WebDAV | Existing file managers and compatible applications | Confirm against your client before relying on it |
| CLI and API | Scripts, automation, and administration | Use scoped tokens where possible |
Versions and recovery
Local storage can retain earlier versions of changing files, giving you a way back after an accidental overwrite. Version history is designed as a recovery convenience, not a replacement for backups.
Version history is currently local-storage only. Remote storage backends may have their own version behavior, but FileYard does not present that as one uniform guarantee.
Run your way
Start small with a single Go binary and SQLite. Move metadata to PostgreSQL when your deployment needs it. SMTP, OIDC, and other integrations remain optional rather than becoming prerequisites for a useful server.
Each space can choose an appropriate storage backend. This makes it possible to keep a fast working set on local disk while connecting other storage where it fits—without pretending that migrations between every backend are already effortless.
What FileYard does not promise
FileYard is not a cloud-drive service, an off-site backup provider, or a finished replacement for every collaboration suite. It is a focused file server with sharing, sync, and practical integrations. The project favors a clear boundary over an endlessly expanding platform.