The short answer: Android 11 and newer include Notification history under Settings → Notifications. It is switched off by default, it only records from the moment you enable it, and it holds roughly the last 24 hours. Turn it on now and it will be there the next time you swipe something away by accident.
Almost everyone has done it: a notification arrives, your thumb clears the shade, and half a second later you realise you never read it. Whether you can get it back depends entirely on one toggle — and on whether you flipped it before the mistake, not after.
Turn on Notification history
On a Pixel or most stock-ish Android builds:
Settings → Notifications → Notification history → turn on Use notification history.
Manufacturer skins move it a level or two:
- Samsung (One UI): Settings → Notifications → Advanced settings → Notification history
- Xiaomi / HyperOS, OnePlus, Oppo: usually Settings → Notifications & Control Center → Notification history, though some builds omit the feature entirely
- Nothing, Motorola, Sony: generally follow the stock path above
Once it’s on, the same screen becomes the log. It lists recent notifications and, below them, the ones you snoozed or dismissed in roughly the last day — app by app, with a timestamp.
If you can’t find it anywhere in Settings, try searching Settings for “history”. If nothing comes up, your build doesn’t ship it, and the longer-term option further down is the only route.
What it does not do
This is where most people get caught out. Notification history is genuinely useful, but it’s a short-term safety net rather than an archive:
- It records nothing from before you turned it on. There is no hidden backlog waiting to be revealed — enabling it after losing a notification will not bring that one back.
- It keeps about 24 hours. Anything older is gone. There is no setting to extend the window.
- It logs text, not media. Photos, stickers and other attachments that arrived with a notification generally aren’t preserved.
- Apps can remove their own notifications. Read a WhatsApp message on your laptop and the phone notification is withdrawn by the app itself.
- It’s a flat list. One long chronological log across every app, with no grouping by who the message was from.
On Android 10 and older
Older versions had no user-facing history screen, but there was a well-known trick: add a Settings shortcut widget to the home screen and pick Notification log from the list of targets. That opened a raw system log of recent notifications.
It disappeared with Android 11, replaced by the proper Notification history feature. If you’re on an older phone, the widget route is worth trying; on anything current, it’s gone.
Why notifications disappear in the first place
Worth separating the causes, because two of them are fixable:
- You or the app cleared it. Normal, and what history is for.
- Do Not Disturb was on. The notification arrived silently. It’s in the shade, not lost.
- The app was killed in the background. Aggressive battery optimisation on Xiaomi, Samsung and similar builds can stop an app being able to deliver at all. That’s a settings problem, not a history problem.
- A message was deleted for everyone. In WhatsApp and Telegram, the notification is often the only remaining copy of what was said — and that’s precisely the case where a 24-hour window is not much comfort.
Keeping notifications for longer than a day
If a day isn’t enough, the mechanism you need is a notification listener: an app that receives each notification as it arrives and writes it down.
That’s the basis of NotiWeave. It saves the notifications from the apps you choose and groups them into a thread per sender, so a week of messages from one person reads as one conversation rather than scattered log entries. Photos, stickers and shared reels land in the thread alongside the text. Nothing expires on a timer — entries stay until you delete them.
Getting there:
- Grant Notification Access on first launch. It’s the one permission needed to read notifications, and it can be revoked at any time.
- Allow background running so capture keeps working while the phone is idle — on Xiaomi-style builds, that includes Autostart. The app walks you through it.
- On the Apps screen, tick the apps whose messages you want saved as threads. Everything you don’t tick stays invisible to it.
Two honest limits: it can only save what arrives after you’ve set it up — there’s no way for any app to reach back in time — and it’s Android-only, because iOS gives apps no mechanism to read other apps’ notifications at all.
Everything stays on the device. There’s no account and no server, which is spelled out in the privacy policy.
Common questions
Can I recover a notification I cleared before enabling history? No. Nothing was being recorded, so there’s nothing to recover. This is the one case where no app or setting can help.
Does notification history show deleted WhatsApp messages? If the notification arrived within the window history covers, the text will usually still be listed there — the notification is a separate copy from the message in the chat.
Does it cost battery? Negligibly. Both the system feature and a listener app react to notifications you already receive; nothing is being polled.
Can I see notification history for one specific person? Not with the built-in feature — it’s a single flat list. Grouping by sender is exactly what a per-sender threading app adds, and it pairs well with giving each person their own notification sound.
Turn the system toggle on today regardless of anything else you do — it costs nothing and it’s the difference between “gone” and “annoying” the next time your thumb is faster than your eyes.