Windows doesn't give you a way to export your notification history. Once the Action Center is cleared, those alerts are gone. Notification Logger captures every notification as it arrives and lets you export the full history to a CSV file with a single click — for backup, compliance, analysis, or record-keeping.

Why Export Your Notification History?

A notification log export is useful in more scenarios than it might first seem:

Security audit trail

Export Windows Defender, firewall, and antivirus alerts to document a timeline of security events on a machine. Useful for incident response and IT investigations.

Developer debugging

Applications and CI/CD pipelines send build results, error notifications, and deployment status as Windows toasts. Exporting creates a log that can be diff'd against previous runs.

Notification pattern analysis

Load the CSV into Excel, Google Sheets, or a BI tool. Pivot by app name, hour of day, or keyword frequency to understand which apps are the most disruptive to your workflow.

Compliance and documentation

Regulated environments may require evidence that certain alerts were received and reviewed. A timestamped CSV export provides that paper trail.

Personal backup before reinstalling Windows

Before a clean Windows install, export your notification history so you don't lose the log of everything that happened on the old system.

How to Export Your Notification History

  1. Open Notification Logger from the Start menu or system tray.
  2. Optionally type a search term to export only the notifications that match it. Column filters and the Favorites view do not limit the export.
  3. Click the Export button in the toolbar (the save/arrow icon).
  4. In the Save dialog, choose a folder, a file name and the format, CSV or JSON.
  5. Click Save. The file is written immediately.
  6. Open the file in Excel, Notepad, or any CSV-capable tool.
Export filtered results: Type your search term before clicking Export. The file will contain only the notifications that match it — not the full history. This makes it easy to export just the security alerts, for example.

What's in the CSV File

Each row in the exported CSV represents one notification. The columns are:

Column Description Example value
NotificationDate When Windows created the notification, in local time 2026-05-06T14:32:07.1830000
App Name of the application that sent the notification Microsoft Outlook
IsFavorite Whether the notification is starred True
NotificationText Notification text Sarah: Can you send the updated…

Analysing Your Export in Excel

Once the CSV is open in Excel, a few quick analyses are worth running:

Which apps send the most notifications?

Insert a PivotTable with App as the Row field and Count of App as the Value. Sort descending. You'll immediately see your top notification sources — often the result surprises people.

When do notifications peak?

Add a calculated column extracting the hour from the timestamp (=HOUR(TIMEVALUE(MID(A2,12,8)))), then pivot by that column. This reveals whether your notification flood happens at 9 am, after lunch, or late evening.

Keyword frequency

Use COUNTIF with wildcard patterns to count how many notifications mentioned specific words: =COUNTIF(D:D,"*error*"). Build a small keyword report to identify the most common alert types.

Privacy note: Your exported CSV stays on your own machine. Notification Logger has no network code and sends nothing to any server. The file is yours to keep, delete, or share as you choose.

Keeping Notifications Beyond the Retention Window

By default, Notification Logger deletes notifications older than 14 days to keep the database lean. If you need a longer in-app history, change the retention period in Settings — it can be set to any number of days.

For long-term archiving, the recommended workflow is to run a weekly export and save the CSV files to a folder on your machine or cloud drive. This way you retain a permanent record independent of the app's database size.

Notifications marked as Favorites are never automatically deleted, regardless of the retention setting. Use Favorites to preserve specific notifications indefinitely without relying on exports.

Frequently Asked Questions

Can I export only notifications from one app?
Yes. Type the app's name in the search box, then click Export: the file contains only the notifications that match the search. Search also matches notification text, so a few notifications from other apps that mention the name can be included; remove them in Excel. The App column filter and the Favorites view change only what the list shows, not what is exported.
Can I choose the export folder?
Yes. Export opens a standard Save dialog, where you choose the folder, the file name and the format: CSV or JSON.
Can I import the CSV back into Notification Logger?
No — the export is one-way, for archiving and external analysis. The app does not support CSV import.
Does the export include notifications I've deleted?
No. The export reflects what is currently in the database. Manually deleted notifications and those that expired under the retention policy are not included.
How large does the CSV get?
It depends on how many notifications you receive. A typical knowledge worker on a 14-day retention window might accumulate 2,000–5,000 notifications, producing a CSV of roughly 500 KB–2 MB. With a longer retention window or high-notification apps it will be larger.
Is the notification data encrypted at rest?
Notification Logger stores data in a local SQLite database without additional encryption. If you require encryption, encrypt the drive or folder using Windows BitLocker or a third-party tool.

Start logging and exporting your Windows notification history today

Download Notification Logger