Darkify · Version history
Darkify changelog and version history
- Latest version
- 2.2.5
- Nov 2, 2026 (6 days ago)
- Releases
- 62
- since 2024
- In the last year
- 35
- about one every 10 days
- Tested up to
- WordPress 7.1.4
- PHP 7.1 or later
Releases each year
- 20246 releases
- 202526 releases
- 202630 releases
202630 releases
Darkify 2.2.5Latest
- Added: Plugin automate release with 10up
Darkify 2.2.4
- New: Show Block Editor Palette setting (Controls → Admin, under Block Editor Dark Mode). Turn it off to hide the palette dropdown from the block editor toolbar; the editor then always uses the palette chosen in Block Editor Palette. On by default, so nothing changes until you turn it off.
Darkify 2.2.3
- Fixed: On sites with thousands of posts the Darkify settings screen showed “Failed to load settings. Please refresh.” The post lists used by the Allow Only Posts and Disallowed Posts options loaded every post in full and ran out of memory. They now load only post titles.
Darkify 2.2.2
- Fixed: Since 2.2.1 some themes (for example Hello Elementor) could override the floating switch’s look with their own button styles: the Switch Border radius setting had no effect, a thin border appeared, and the icon could lose its centering. The switch now keeps the shape, size and border set in…
Darkify 2.2.1
- Improved: Accessibility. Every dark mode switch (floating, mobile, menu, shortcode, Gutenberg block and Elementor widget) is now a real button. It can be reached with Tab, used with Enter or Space, and is announced by screen readers as “Dark mode” with its on/off state. Keyboard focus shows a visib…
- Improved: Accessibility. The admin bar dark mode toggle can now be reached and used with the keyboard, and screen readers announce it with its on/off state.
- Improved: Accessibility. The block editor palette picker now works with the keyboard (arrow keys, Home/End, Enter, Escape).
- Improved: The switch attention effect now plays briefly after the page loads instead of looping forever. All switch animations follow the “Reduce motion” system setting.
- Fixed: A keyboard shortcut without Ctrl or Cmd (such as Shift+D) toggled dark mode while visitors typed in forms. It is now ignored inside text fields.
- Fixed: The keyboard shortcut no longer replaces keyboard handlers added by the theme or other plugins.
- Removed: The bundled Polish translation. Translations are now provided through translate.wordpress.org, where anyone can contribute.
- Developer: New darkify_switch_label filter to change the switch’s accessible name.
Darkify 2.2.0
- Added: URL Parameter option under Controls → Frontend. Add ?darkmode=1 or ?darkmode=0 to any page URL to open it in dark or light mode. The parameter name can be changed.
- Added: Include Images, Include Videos, and Exclude Videos options for Brightness and Grayscale are now shown under Media as Pro options.
- Improved: Tooltip Position now shows only the two positions that fit the selected Switch Position, so the tooltip never opens off screen.
- Tested: Compatibility with WordPress 7.1.3.
Darkify 2.1.3
- Fixed: Restored smooth transitions and animations for accordions, dropdowns, hover states, and other interactive elements while preventing unwanted color transition effects during initial Dark Mode rendering.
- Fixed: Prevented the light theme from briefly appearing before Dark Mode is applied on slow or uncached page loads.
- Fixed: Disallowed Elements and elements with the darkify_ignore class are now completely excluded from Darkify processing, including their child elements. Darkify classes, data attributes, and inline styles will no longer be added to them.
- Fixed: Replace Individual Colors no longer disables hover colors. Pinned colors now apply correctly while hover states continue to work.
- Fixed: Menu Switch → Menu Select now supports classic WordPress menus, block theme navigation menus, and Kadence Navigation menus.
- Fixed: A dark mode switch placed in a footer, sidebar or menu still rendered while Frontend Dark Mode was turned off — as an unstyled, unresponsive control, since the stylesheet and script it needs are exactly what that setting stops loading. Every other entry point already checked the setting; the…
- Fixed: A colour pinned under Replace Individual Colors with Apply To set to Icons only did nothing on icons whose colour already read clearly against the page — Elementor’s Icon List being the plain case, its default blue staying blue. The icon writer measured contrast first and stopped there whene…
- Fixed: Two colour overrides pinned to near-identical colours collapsed into one — #ffffff and #fffffe were treated as the same colour, so the second rule silently never applied. Matching allowed about five percent of drift per channel, on the reasoning that a colour typed from a design tool or roun…
Darkify 2.1.2
- Fixed: Admin dark mode did nothing on the admin screens of Fluent Forms, FluentCRM, Fluent Booking, FluentSMTP and WP Social Ninja, and the admin-bar toggle reported an error when clicked. Each of those plugins runs a “no-conflict mode” that removes every script served from the plugins directory on…
- Fixed: With a colour preset selected, the current item in Darkify’s own settings sidebar was invisible, as was the highlight on a hovered menu entry. Preset colours are pushed into the screen’s design tokens, and the selected-item token was being handed the same value as the surface behind it — so…
- Fixed: Switching Admin Panel Dark Mode off left the settings screen in a broken half-state — dark cards and unreadable text on a light page — until it was reloaded. Turning the option off returned the page to light but left the preset’s colours written into the screen’s tokens, because the engine t…
- Fixed: With a colour preset selected, links inside admin notices stayed WordPress blue while every other link took the preset’s colour. WordPress styles notice links more specifically than plain links, and the darkening engine marks everything it rewrites as important — so Darkify’s own rule no lon…
Darkify 2.1.1
- Fixed: Primary buttons, switches and selected states on Darkify’s own settings screens ignored the Admin Panel Palette and stayed on a near-white default. Those parts are drawn from a --primary / --primary-foreground pair, and the pair had been left out of the palette map on the grounds that overwr…
- Fixed: Switch tracks and thumbs rendered transparent under some palettes. A palette that did not carry a field was still writing that field’s variable, as the literal text undefined, and a custom property that parses but never resolves takes its whole declaration down with it — so the track did not…
- Fixed: Toggles were hard to see once they did have a colour, because the checked track took the palette’s button fill — a colour chosen to sit on the page background, not to be read at a glance against a card, and measuring between 1.21 and 2.86 against each palette’s card. The track now takes the…
- Fixed: Changing a colour preset in Live Preview only partly applied until the preview was reloaded. Rules written in terms of Darkify’s variables follow a preset instantly, but the engine also writes colours inline as it walks the page — gradients, shadows, overlays, image brightness, icon colour —…
Darkify 2.1.0
- Changed: Dark mode in wp-admin is now rendered by Dark Reader instead of the per-element engine. The old engine walked every element on the screen, read its computed style, and re-walked on any DOM change — workable on a page that settles, and untenable in wp-admin, which never does. Dark Reader wo…
- Fixed: The block editor became unresponsive with Admin Panel Dark Mode on, and stayed that way — typing, adding a block or opening the inserter could each trigger it. Every DOM change queued a fresh walk of the whole editor, each visited element forcing a style recalculation, and the editor changes…
- Added: Admin Panel Palette and Block Editor Palette settings, chosen independently. Both default to Auto, which derives a colour for every colour on screen rather than pinning a background and a text colour — that derivation is what lets unfamiliar admin screens from other plugins come out right, a…
- Fixed: The classic editor’s dark mode button did nothing whenever the admin itself was light. Its state had been folded into the admin’s, so a light admin ruled out a dark writing area — a combination people deliberately choose. The two are independent again, and the editor body now follows the cho…
- Fixed: Short admin screens were painted in two tones, with a horizontal seam roughly a screen-height down. WordPress colours body and leaves html unpainted, so the two were being darkened from different starting points and the join showed wherever the content was shorter than the window. Both now r…
- Fixed: Darkify’s own settings screens rendered card borders and toggle backgrounds in red. Those screens ship their own dark theme, so darkening them a second time layered two themes over each other — and the modern colour values they use could not be parsed by the darkening engine, leaving the unr…
- Fixed: The Darkify menu icon in the WordPress sidebar sat noticeably brighter than every other icon. WordPress renders a menu icon as a background image, which cannot take the menu’s colour the way its own font icons do, so ours stayed flat white. It now takes its colour from the menu like everythi…
- Fixed: Resizing the browser window could freeze the page outright. Whether the admin menu needs its own scrollbar is a measurement that its own answer changes, and with a single threshold a menu sitting near that boundary flipped between the two answers without ever settling — a resize drag holds i…
- Changed: The block editor has one dark mode toggle instead of two. The admin bar carried a second one alongside the toolbar button, both doing the same thing. The toolbar button is the one that survives, because the admin bar is hidden in the editor’s fullscreen mode — which is its default.
- Fixed: The Help screen collapsed awkwardly at narrower widths — review cards wrapping to a word per line, plugin titles crushed against their install button, a tab clipped mid-word behind the upgrade button. Each of those laid itself out from the browser window’s width while sitting in a column tha…
- Fixed: Several Help screen elements were unreadable in dark mode: video play buttons vanished into their own white circles, the Lite vs Pro table header became a bright white band, and hovering a plugin card drew a hard white outline. Each used a colour that inverts between light and dark against s…
- Added: Pro colour presets now appear in the palette pickers as locked, badged entries rather than being absent. They cannot be selected or saved, and the engine falls back to Auto if one is ever set.
- Fixed: The “Upgrade To Pro!” menu link replaced the current admin screen instead of opening in a new tab, losing whatever was being configured.
Darkify 2.0.4
- Fixed: Brand-coloured icons — star ratings, coloured logo marks — lost their colour and read as the same flat grey as body text. The icon recolouring introduced in 2.0.4 mapped every icon onto the page’s text colour unconditionally, with no exception for a colour that was never meant to blend in; a…
- Fixed: A background writer added in 2.0.4 for empty decorative overlay divs (Elementor’s .elementor-background-overlay and similar) was also catching real, content-bearing elements that simply never picked up one of the class-based repaint’s own classes — a countdown timer’s number box, a page-buil…
- Fixed: A dark icon sitting on its own light background — a WordPress social icon link’s circle, for instance — was being recoloured to the page’s light text colour, because the contrast check only looked at the page’s general dark backdrop, not what the icon is actually sitting on. That turned a pe…
- Added: Border Color and Hover Border Color controls for buttons, in every color preset. A button’s border was the one color dark mode never touched, so an outline button kept its light-design brand edge — a bright ring around a dark fill — and no setting could reach it. Each preset now ships a bord…
- Fixed: Card outlines drawn as a shadow ring (0 0 0 1px) disappeared in dark mode. A ring like that is a border written in the wrong property, and it was being painted black like a real shadow — black on near-black is nothing at all — so a card outlined this way lost its edge while the card beside i…
- Fixed: Body text and headings came out tinted on themes whose text color is a tinted near-black — inks like #0A232A or #101828, which most modern themes use instead of pure black. Those read as highly saturated brand colors and were lifted to a light teal or blue, overriding the text color chosen i…
- Fixed: Hover effects, dropdowns, sliders and reveal animations snapped to their end state instead of easing. Darkify pauses CSS transitions while it reads a page’s real colors, and that pause was applied to the whole document — including elements the pass never looked at — on passes triggered by an…
- Fixed: Live Preview hid the site header on many themes. The panel filters out cookie banners, chat widgets and popups so the preview shows the page itself, and headers named “sticky-bar”, “top bar” and similar were caught by that filter — hiding the part of the page most worth previewing. Semantic…
Darkify 2.0.3
- Fixed: Pages could freeze or crawl once dark mode was on, worse the larger the page. Every element was watched for class changes individually, and each watcher had to be re-registered across the whole document whenever anything changed — on a 2,929-element page that came to 1.23 million registratio…
- Improved: Pages that keep changing after load — infinite scroll, carousels, WooCommerce cart and fragment refreshes, page builders and anything React-rendered — no longer re-scan the entire document on every change. Only the newly inserted parts are examined, so a long page stays as responsive as a…
- Improved: Switching between light and dark now only revisits the elements Darkify actually styled, and reads each one’s colours once instead of twice, so the toggle settles noticeably faster on large pages.
- Fixed: The dark mode toggle snapped between states instead of animating. Darkify pauses CSS transitions while it reads a page’s real colours, and the switcher was being caught by that pause even though its colours are never read.
- Improved: Pausing transitions during a pass is now a single rule on the page root rather than an inline style written to and removed from every element, which removed one forced style recalculation per element from every pass.
- Changed: The screen no longer dims while a page loads in dark mode. The brightness baseline added in 2.0.2 covered the gap before the first pass, but on a slow page it read as a grey overlay sitting over the whole site until loading finished, and it returned on every navigation. The page background…
- Added: A developer diagnostics mode for support and debugging, off by default and invisible to visitors. Add ?darkify_debug=1 to any URL, then run darkifyDebug.report() in the browser console for pass counts, timings and the number of elements Darkify processed.
- For releases before 2.0.3, see the full changelog: https://plugins.svn.wordpress.org/darkify/trunk/changelog.txt
Darkify 2.0.2
Darkify 2.0.1
Darkify 2.0.0
Darkify 1.5.5
Darkify 1.5.4
Darkify 1.5.3
Darkify 1.5.2
Darkify 1.5.1
Darkify 1.5.0
Darkify 1.4.26
Darkify 1.4.25
Darkify 1.4.24
Darkify 1.4.23
Darkify 1.4.22
Darkify 1.4.21
Darkify 1.4.20
Darkify 1.4.19
Darkify 1.4.18
202526 releases
Darkify 1.4.17
Darkify 1.4.16
Darkify 1.4.15
Darkify 1.4.14
Darkify 1.4.13
Darkify 1.4.12
Darkify 1.4.11
Darkify 1.4.10
Darkify 1.4.9
Darkify 1.4.8
Darkify 1.4.7
Darkify 1.4.6
Darkify 1.4.5
Darkify 1.4.4
Darkify 1.4.3
Darkify 1.4.2
Darkify 1.4.1
Darkify 1.4.0
Darkify 1.3.5
Darkify 1.3.4
Darkify 1.3.3
Darkify 1.3.2
Darkify 1.3.1
Darkify 1.3.0
Darkify 1.2.5
Darkify 1.2.4
20246 releases
Darkify 1.2.3
Darkify 1.2.2
Darkify 1.2.1
Darkify 1.2.0
Darkify 1.0.1
Darkify 1.1.0
Questions about Darkify’s releases
What is the latest version of Darkify?
2.2.5, released on Nov 2, 2026 (6 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.1 or later.
How often is Darkify updated?
35 releases in the last year, about one every 10 days. Its first release on WordPress.org dates from June 2024.
Know when your rivals ship
Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.
Start freeRelease dates come from the day each version’s folder was made in Darkify’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.