Disable Admin Notices Plugins Compared: Hide, Capture or Mute?
Three plugins, three philosophies. One hides it all, one lets you mute each nag, one files them in an inbox. Which fits depends on how much you trust yourself to check.
On this page
Picking a disable admin notices plugin comes down to one question: when a notice is hidden, where does it go? The three popular answers are nowhere, a panel, or an inbox. All three stop the dashboard looking like a billboard. They differ in what happens the day a real warning arrives. This comparison covers the two most installed notice managers and our own, with the trade-offs stated plainly.
We make DevDome Admin Cleaner, so the other two come first.
Disable Admin Notices Individually (Webcraftic)
The most installed option and the simplest. Every notice gets a “hide” link; click it and that notice stays hidden for you. A settings page offers a global switch that hides all notices, and a second one that hides notices from specific plugins.
Where it is better. It is tiny and it does exactly one thing. If your problem is three persistent nags from three plugins, hiding each once solves it in a minute.
Where it falls short. Hidden means gone. There is no place to read what you hid, so a hidden notice that later turns into a real warning is invisible. The global switch is the trap: convenient on a noisy site, and then a failed update notice never reaches you. Per-plugin hiding has the same problem, since the plugin you silenced is also the one that will tell you its licence expired.
Admin Notices Manager (Melapress)
This one takes a different line: notices are not hidden, they are moved. A badge in the toolbar shows a count, and clicking it slides out a panel with every notice. Settings let you choose, by notice type, whether to show in the panel, show inline as before, or hide.
Where it is better. Nothing is lost. Every notice is still readable, one click away. For a site owner who wants quiet but not blindness, this is a sound design. Per-type rules mean you can keep error notices inline and send everything else to the panel.
Where it falls short. It handles notices and nothing else. Dashboard widgets, toolbar clutter, footer text and plugin-list nag rows stay. There is no mute, so the same marketing banner sits in the panel every day, and no snooze. It is also per-site configuration with no client-mode concept.
DevDome Admin Cleaner
Our approach combines the inbox idea with the rest of the cleanup. Notices are captured into a Notice Inbox that records the source plugin, a classification and the mute status. You hide a notice for yourself or for all administrators, mute it permanently, or snooze it for one or seven days. Auto-hide catches notices injected after page load, which is how some plugins get past simple filters. Notice hiding applies only to users who can access the plugin, so editors see what their role normally shows.
Beyond notices, a Clean My Admin action hides dashboard widgets, supported toolbar items, footer details and plugin-list notice rows at once, and Client Mode hides selected admin menu items for chosen roles without changing their permissions. No account is needed.
Where it is better. One plugin for the whole admin, with snooze and mute, and the per-role control that client sites need.
Where it falls short. It is more plugin than a site with one annoying nag needs. If you only want three notices gone, the Webcraftic tool is lighter.
Where the notices come from
It helps to know what you are managing. WordPress has one hook for admin notices, and core itself uses it for the messages that matter: an update that failed, a PHP version that is too old, a missing extension, a site health warning. Plugins use the same hook for everything else: licence renewals, review requests, “connect your account”, seasonal discounts and announcements of their other products. The directory guidelines ask authors to keep nags dismissible and limited, but enforcement is light and premium plugins outside the directory follow their own rules.
Two technical wrinkles explain why some notices survive simple filters. First, a notice that the author re-creates with a new identifier on every update looks new to a tool that remembers dismissals by ID, which is why muting by source or content is more durable. Second, some plugins inject banners with JavaScript after the page has loaded, so a filter that runs when the page is built never sees them; only a tool that watches the page afterwards catches those.
Testing a notice manager in ten minutes
Install the candidate on a staging site or a quiet afternoon. Trigger a real core notice if you can, for example by pausing an update, and confirm you can still find it after the manager is active. Dismiss or mute the noisiest plugin banner and reload twice to see whether it stays gone. Update a plugin that is known to re-show its banner and check again. Log in as an editor and confirm nothing changed for that role. Finally, if you manage client sites, check whether hiding is per user or for everyone, because the wrong default means a colleague loses the licence warning you muted for yourself. Ten minutes answers the only question that matters: will the real warning still reach me after the noise is gone.
Side by side
| Disable Admin Notices Individually | Admin Notices Manager | DevDome Admin Cleaner | |
|---|---|---|---|
| Hidden notices go | Nowhere | Slide-out panel | Notice Inbox |
| Per-notice hide | Yes | By type | Yes |
| Mute permanently | Effectively | No | Yes |
| Snooze | No | No | 1 or 7 days |
| Global hide switch | Yes | By type | No global blind switch |
| Post-load injected notices | No | No | Auto-hide |
| Widgets, toolbar, footer | No | No | Yes |
| Per-role menu hiding | No | No | Client Mode |
| Source and classification | No | Partly | Yes |
Which to pick
Three nags and nothing else: Disable Admin Notices Individually. Hide them, never use the global switch, done.
You want quiet but still want to read everything: Admin Notices Manager. The panel is a good answer for a single site run by its owner.
Several sites, clients, or a dashboard that needs more than notice handling: DevDome Admin Cleaner. The inbox plus widgets, toolbar and Client Mode covers the whole cleanup in one place.
Whichever you choose, open wherever the notices went once a month. The one that keeps coming back is the one that needs fixing, not hiding.
Key takeaways
- Disable Admin Notices Individually by Webcraftic adds a hide button per notice and a global off switch, and is the most installed option.
- Admin Notices Manager by Melapress moves notices into a slide-out panel so they are still readable, with a count badge.
- DevDome Admin Cleaner captures notices into an inbox with source and classification, mute and snooze, and bundles dashboard, toolbar and menu cleanup.
- The dangerous choice is any global off switch left on: core warnings about failed updates and security issues vanish with the nags.
- If you only want notices handled, the lighter tools are fine. If you want the whole admin cleaned and client-ready, pick the bundle.
Sources
- Disable Admin Notices Individually on WordPress.org : features, install base and the global hide option
- Admin Notices Manager on WordPress.org : the slide-out panel approach
- WordPress Developer Resources: admin_notices hook : the single hook every plugin here intercepts
Links last checked October 17, 2026.
Frequently asked questions
Is it safe to disable all admin notices?
Not permanently. WordPress core uses the same notice system for failed updates, missing PHP extensions and security warnings. A global off switch hides those too. Prefer a tool that keeps notices readable somewhere, or mute them one by one.
Why do notices come back after I hide them?
Some plugins regenerate a notice with a new ID on every update, or ignore the dismiss button entirely. A notice manager that matches by content or source rather than ID keeps it hidden regardless.
Do these plugins work with premium plugins and themes?
Mostly. Anything that uses the standard admin_notices hook is caught. A few plugins print banners directly into their own pages or inject them with JavaScript after load; only tools with a post-load auto-hide option catch those.
Will hiding notices affect editors and clients?
Depends on the tool. Some hide for every user, some per user, some only for administrators. For client sites, choose one with per-role control so the client sees a clean screen and you still see warnings.