mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Screenshot diff uptime monitor type #4421
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#4421
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @forabi on GitHub (Nov 8, 2025).
📑 I have found these related issues/pull requests
N/A
🏷️ Feature Request Type
New monitor
🔖 Feature description
It would be awesome to have a new type of monitor: screenshot diff -- when the monitor is first added, the user uploads a screenshot. Then Uptime Kuma will use Chromium to take a screenshot whenever the monitor runs, and use e.g. pixelmatch library to compare the provided screenshot with the actual one, with some configurable diff tolerance.
✔️ Solution
N/A
❓ Alternatives
No response
📝 Additional Context
No response