[Feature] Server-Level Setting to Block Upload of NSFW Images

[stephenpapierski]

I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.

• Yes

The feature

Feature

Immich already offers excellent AI-powered tagging, including the ability to flag NSFW content. However, current functionality only allows for tagging or hiding sensitive content after upload by users. For deployments where NSFW material is strictly disallowed, a server-level setting to block the upload entirely is needed.

This request proposes a configurable option that would:

• Automatically scan all incoming uploads using the existing AI detection pipeline
• Reject uploads flagged as NSFW (based on a configurable confidence threshold)
• Return a clear error to the client (e.g., “Upload blocked: content flagged as NSFW”)
• Optionally log the rejection event for auditing or admin review

Motivation

If my understanding is correct, server administrators are responsible (and potentially legally liable) for the content stored on their Immich instances, even when uploaded by end users. Without a pre-upload blocking mechanism, NSFW material could be stored either accidentally or intentionally, putting admins at risk of violating internal policies, or even local laws.

A configurable upload blocker would make Immich safer and more suitable for use in:

• Family or shared household setups
• Educational institutions and schools
• Community-hosted or publicly accessible instances
• Business or compliance-bound environments

Platform

• Server
• Web
• Mobile

[bo0tzz]

This isn't really feasible to do, as the ML pipeline runs async some time after the upload. When workflows (#1673) are implemented you might be able to use that for this.

[stephenpapierski]

My main concern is that they don't stay there, so if it's technically infeasible to block upload, then having an option to delete photos that are detected as NSFW would still meet the intention of the request. Will workflows allow you to delete based on criteria, or only put into a smart album based on criteria?

[bo0tzz]

Workflows originally started as the smart albums concept, but the plan is to allow them to do everything we can - delete, archive, favourite, share, and so on.