cresdock
Home Apps Deploy Pricing
Cresdock  /  Apps  /  File Browser
Files & sync

How to self-host File Browser

See, upload and organise your files from the browser. Cresdock runs it on a server you own, from a catalogue, with no Docker and no reverse proxy to configure.

What Cresdock does for you with File Browser

Why run File Browser yourself

Cloud storage is rented, priced per month forever, and readable by whoever runs it. The same files on a server you own cost what the disk cost.

It is also how you retire Dropbox or Google Drive — one line in replacing cloud subscriptions, app by app.

What kind of server File Browser needs

Light on power, heavy on disk — sizing is really a question of how much you want to keep. If your library outgrows the server, Cresdock can put it on cloud storage and keep it looking like a normal folder.

Cresdock itself is undemanding — it runs on a small rented server, an old desktop or a mini PC, on Ubuntu or Debian. Everything it installs shares that machine, so the honest question is not "will this app run" but "how much am I going to put on here in total".

Where to run File Browser

File Browser runs wherever Cresdock runs, and the choice is about the machine, not the app:

Installing File Browser

  1. Put Cresdock on a server

    One line on any Ubuntu or Debian machine — a rented VPS, a spare PC, a home server. It sets itself up.

  2. Pick File Browser from the catalogue

    Click Install. The panel pulls the image, writes the configuration, gets a certificate and starts it.

  3. Open it from your dashboard

    Its address and any login details are on its card. Start, stop, update, roll back or remove it from the same place, any time.

What this replaces

Doing it by hand means writing something like this, then keeping it working:

services:
  filebrowser:
    image: filebrowser/filebrowser:v2.63.18
    restart: unless-stopped
    ports:
      - "80:80"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - ./filebrowser/config:/config
      - ./downloads:/downloads
      - ./media:/media

And that is the easy half. Still to do:

On Cresdock, File Browser is one click and none of the above exists.

Common questions

Do I need to know Docker to run File Browser?

No. Cresdock installs File Browser in one click from its catalogue: it pulls the image, writes the configuration, gets an HTTPS certificate and starts it. File Browser's configuration is written before it first starts, so it opens already set up.

What happens to my files when File Browser updates?

Cresdock changes File Browser's own configuration only. Your downloads and your media are never touched by an update, a rebuild or a reinstall — that is a rule the software enforces, not a promise in a document.

Who can see the files I put in File Browser?

Only you. Your folders belong to your account, other people on the server have their own, and each account's apps run on a private network of their own. Updates and reinstalls never touch what you have stored.

Can I run File Browser at home instead of on a VPS?

Yes. Cresdock runs on a mini PC, an old desktop or anything that boots Debian, behind a normal home router with no port forwarding, and File Browser is reachable on your own network first. A rented server is only needed when File Browser must be reachable from anywhere without a VPN.

Can I remove File Browser later?

Yes. Cresdock removes File Browser in one click, and asks whether to keep its configuration for a future reinstall. Nothing else you have installed is affected.

Looking for what File Browser itself can do? That lives in its own documentation — this page is only about running it.

Pairs well with: Migration Tool  ·  Nextcloud  ·  FlareSolverr

Before you start: where to rent a server  ·  what it needs to run  ·  Cresdock vs CasaOS