SnapOtter

SnapOtter is a self-hosted file toolkit that stores and processes image, video, audio, PDF, and general files on your own server.

  • Media Applications
  • Productivity
  • Tools & Utilities
SnapOtter is a self-hosted file toolkit that stores and processes image, video, audio, PDF, and general files on your own server. It offers a web application with more than 200 tools, an image editor, batch jobs, pipelines, an open application programming interface (API), OpenID Connect / single sign-on, and optional local artificial-intelligence features. It suits homelab users who want centralized, private file management without sending files to third-party cloud services.

Platform availability

Available on 5 of 10 platforms

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.

78/100 Good

Maintained
100last commit 17 days ago
Popular
692,938 GitHub stars
Easy to install
755 install platforms, install notes, Docker image
Light to run
404 GB minimum RAM, runs on ARM

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

GitHub stars
2,938
Open issues
444
Last commit
2026-11-04
Latest release
v2.3.0
License
AGPL-3.0
Activity
rising

Checked 17 days ago - source: GitHub (snapotter-hq/SnapOtter)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 1 CPU core(s), 10 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set a real admin password before starting If you use the Docker Compose file (a setup file that tells Docker what to run), change DEFAULT_PASSWORD from 'changeme' and keep AUTH_ENABLED=true. Without this, anyone who can reach your SnapOtter page can use it and possibly mess with your files. source
  • Keep your files in a saved Docker volume Use the Docker volume mappings for /data and /tmp/workspace, which tell Docker to save those folders outside the app. This keeps SnapOtter’s data and settings around after restarts or when the container is recreated. source
  • Open the app on port 1349 Keep the 1349:1349 line in the Docker settings so your computer’s port 1349 forwards to SnapOtter. Your browser can then open the app at your server’s address plus :1349, and if 1349 is taken you can change the left side to a free number. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What port should I expose for SnapOtter in Docker?

SnapOtter listens on container port 1349. Keep the host-to-container mapping as 1349:1349, or change only the host-side number if 1349 is already in use.

How do I enable authentication when using Docker Compose?

Change DEFAULT_PASSWORD from the placeholder changeme and keep AUTH_ENABLED=true. Otherwise, anyone who can reach the SnapOtter page can use it and alter files.

Where is GPU setup documented?

The docs link to a GPU and Compose setup guide and a Docker tags and GPU section.

Answers sourced from docs.snapotter.com, github.com

Community

Collected 54 days ago - public community threads