← Directory

Lemmy-UI

Lemmy-UI is the official web frontend for Lemmy, an open-source, federated, Reddit-style link aggregator and forum.

  • Communication
  • Media Applications
Lemmy-UI is the official web frontend for Lemmy, an open-source, federated, Reddit-style link aggregator and forum. It gives self-hosters a familiar interface to browse communities and lets administrators and moderators manage posts, comments, users and reports on their own instances.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (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.

74/100 Good

Maintained
100last commit 1 day ago
Popular
601,014 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
801 GB minimum RAM, runs on ARM

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

GitHub stars
1,014
Open issues
53
Last commit
2026-10-14
License
AGPL-3.0
Activity
declining

Checked today - source: GitHub (LemmyNet/lemmy-ui)

Resources & Compatibility

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

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

First-install notes

  • Create and edit .env.local first Copy example.env.local to .env.local and fill in your site settings before starting the UI. This file is where the app reads things like your public address and backend location, so missing or wrong values can make the page fail or point users to the wrong place. source
  • Point the UI at the Lemmy backend Set LEMMY_UI_LEMMY_INTERNAL_HOST, the address the UI uses to reach the Lemmy server, to something like localhost:8536, and set LEMMY_UI_LEMMY_EXTERNAL_HOST to the address visitors use. If these do not match, the page may open but logins, posts, and shared links can break. source
  • Set HTTPS for secure sites Set LEMMY_UI_HTTPS=true when visitors reach your UI over HTTPS, the secure protocol shown by https:// in the browser. A mismatch can make the browser block some parts of the page. source

Fetched 16 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which file should I prepare before starting Lemmy-UI?

Copy example.env.local to .env.local and fill in site settings before starting the UI. This file provides values such as the public address and backend location.

What should I check if Lemmy-UI opens but logins, posts, or shared links fail?

Check that LEMMY_UI_LEMMY_INTERNAL_HOST points to the address Lemmy-UI uses to reach the backend, such as localhost:8536. Also check that LEMMY_UI_LEMMY_EXTERNAL_HOST points to the address visitors use.

What can cause the browser to block parts of Lemmy-UI when visitors use HTTPS?

A mismatch in the HTTPS setting can block some parts of the page. Set LEMMY_UI_HTTPS=true when visitors reach your UI over HTTPS.

Why might a community be missing from the All feed in Lemmy-UI?

It may not appear until a logged-in user searches for it in the Lemmy-UI web search bar. That causes the server to discover it and start syncing posts, making it searchable and available in apps.

Answers sourced from github.com, github.com, www.reddit.com

Community

Collected 16 days ago - public community threads