MinIO Console

A lightweight web-based dashboard and object browser for managing MinIO object storage clusters, built for self-hosted users.

  • Cloud
  • Tools & Utilities
A lightweight web-based dashboard and object browser for managing MinIO object storage clusters, built for self-hosted users.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

37/100 Low

Maintained
43last commit 298 days ago
Popular
3879 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 12 days ago

GitHub stars
79
Open issues
5
Last commit
2026-01-26
Latest release
v1.8.1
License
AGPL-3.0
Activity
stale

Checked 5 days ago - source: GitHub (huncrys/minio-console)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set login user/password and folder Set MINIO_ROOT_USER and MINIO_ROOT_PASSWORD, then start MinIO with a storage folder such as /mnt/export. These are your first admin login and the place files are saved; without them the server will not start, and losing that folder means losing your files. source
  • Use one folder for a simple start For a simple first install, start MinIO with a single folder, not a multi-drive command like /data{1...12}. A multi-drive command expects every listed folder to exist, and MinIO will not start if they are missing. source
  • Helm toy install is test-only The sample Helm command disables persistence, so saved files can disappear when the test setup is removed. Use it only to try MinIO quickly, and set your root user/password before using it for anything you care about. source
  • Setup Create a dedicated console user via mc, assign an admin policy, then start the Console service with that user's credentials. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need a separate MinIO user and policy before running MinIO Console?

Yes. Create a dedicated MinIO user such as console with a secret key, then assign it an admin policy for testing. Do not use MinIO's Operator Credentials.

Which environment variables must be set before starting the console service?

Set CONSOLE_PBKDF_PASSPHRASE and CONSOLE_PBKDF_SALT to encrypt the JWT payload, and set CONSOLE_MINIO_SERVER to your MinIO endpoint.

Will files persist in the sample MinIO Helm install?

No. The sample Helm install disables persistence, so saved files can disappear when the test setup is removed. Set your root user and password before using it for anything you care about.

Why is the admin UI missing after using Coolify's MinIO deployment?

Coolify dropped MinIO, and the community console lost its admin UI. You can deploy a patched MinIO on Coolify to get the full console back.

Answers sourced from github.com, github.com, learnwithhasan.com

Community

Collected 48 days ago - public community threads