Lemmy · Rate Limits

Lemmy Rate Limits

Lemmy rate limits are configured per instance by the instance administrator and enforced at the application layer. Default values observed from public instances (including lemmy.world running v0.19.18) cover message sending, posting, registration, image uploads, comments, and search. There is no global Lemmy rate limit; each instance operator may tune or disable limits. Exceeded limits return HTTP 429 Too Many Requests.

Lemmy Rate Limits is the machine-readable rate-limit profile for Lemmy on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 6 rate-limit definitions, measuring requests.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Communities, Federated, Fediverse, Rate Limiting, and Social Networks.

6 Limits Throttle: 429
CommunitiesFederatedFediverseRate LimitingSocial Networks

Limits

Comments per-ip
requests
50
Search per-ip
requests
100
Messages (private messages) per-ip
requests
30
Posts per-ip
requests
30
Registration per-ip
requests
5
Image Uploads per-ip
requests
50

Policies

Instance-Configurable Limits
All rate limits are set in the instance's configuration. Operators may increase, decrease, or effectively disable limits by setting high values. There is no enforced global minimum or maximum.
HTTP 429 on Throttle
When a rate limit is exceeded, Lemmy returns HTTP 429 Too Many Requests. Clients should apply exponential backoff before retrying.
JWT Authentication Recommended
Authenticated requests (JWT bearer token) may have different or more lenient rate limits at the instance operator's discretion compared to unauthenticated requests.
Registration Captcha
New account registration is subject to CAPTCHA on many public instances (e.g., lemmy.world uses hard-difficulty CAPTCHA) in addition to the rate limit.

Sources