Firefox is for people who make their own choices online, from what stays private to the tools that help get things done. That commitment to choice shows up throughout the Firefox experience, and AI controls is just the latest example — making it possible to turn generative AI features off, on, or customize them feature by feature.
Over the coming weeks, we’ll be rolling out a series of updates that build on that. Expect more control where it matters, better protections in the background, and a few new tools that make everyday browsing better. You may even spot a fresh face of Firefox along the way.
Here’s a quick look at what to watch for:
An easier way to personalize Firefox
The Settings section has been improved with clear navigation and search, so it’s simpler to customize Firefox. Available in Firefox Nightly starting in April
Privacy upgrades, built in
A freebuilt-in VPN is coming to Firefox. Free VPNs can sometimes mean sketchy arrangements that end up compromising your privacy, but ours is built from our data principles and commitment to be the world’s most trusted browser. It routes your browser traffic through a proxy to hide your IP address and location while you browse, giving you stronger privacy and protection online with no extra downloads. Users will have 50 gigabytes of data monthly in the U.S., France, Germany and U.K. to start. Available in Firefox 149 starting March 24.
Smart Window, previously called AI Window, uses AI to give quick help while you browse — like quick definitions, article summaries, product comparisons and more — without leaving the page. It’s completely optional to use and will be opt in. Waitlist now open for updates and early access.
Split view puts two webpages side by side in one window, making it easy to compare, copy and multitask without bouncing between tabs. Rolling out in Firefox 149 on March 24.
Tab Noteslet you add notes to any tab, another tool to help with multitasking and picking up where you left off. Available in Firefox Labs 149 starting March 24.
“The roadmap for Firefox this year is the most exciting one we’ve developed in quite a while. We’re solely focused on building the best browser, and our features over the next few months and beyond are driven by the feedback from our community,” said Ajit Varma, head of Firefox. “We’re improving the fundamentals like speed and performance. We’re also launching innovative new open standards in Gecko to ensure the future of the web is open, diverse, and not controlled by a single engine. At the same time we’re prioritizing features that give users real power, choice and strong privacy protections, built in a way that only Firefox can. And as always, we’ll keep listening, inviting users to help shape what comes next and giving them more reasons to love Firefox.”
Firefox is also getting a fresh new look across our website, product and beyond. This includes updated themes, icons, and visual refinements across Firefox, including our toolbars, menus, and the homepage. It also brings usability improvements that make key features easier to access. The changes reflect user feedback and aim to modernize the browser while reinforcing a more distinctly Firefox look and feel. We appreciate the community feedback on the designs. We’ll be sharing more soon.
You also may have noticed something else showing up in Firefox recently: our new mascot, Kit. Kit is your companion in this new internet era, our way of making Firefox’s support visible and bringing a little warmth and familiarity as you browse.
More to come
Choosing Firefox means using the internet on your own terms: options when you want them, safety when it matters most, and tools that make the web easier to navigate.
Download the latest version of Firefox to try what’s new, and let us know what you think on Mozilla Connect.
Generative AI tools like GitHub Copilot are not just speeding up coding; they are quietly rewiring how software developers divide their time between writing code, managing projects, and learning new skills.
If you think about it for a moment, it only makes sense that as developers start using AI more, it would change how they spend their time at work. The question is: “How?” Now, thanks to a Harvard Business School working paper, “Generative AI and the Nature of Work,” which surveyed 187,000 open-source developers, we’re getting answers.
The researchers found that programmers given free access to GitHub Copilot significantly shifted their work mix toward hands‑on coding. Before Copilot, developers spent about 44% of their time on coding tasks and 37% on project management, such as triaging issues, reviewing pull requests, and handling support queues. After Copilot arrived, coding time rose by 12.4%, while project management activities fell by 24.9%.
Not all such studies agree with this result. For example, Google’s 2025 DORA State of AI‑Assisted Software Development found that while people using AI produced more code, more quickly, the code also came with more problems, which required more bug-finding and rework.
Other studies agree with this. For example, the development tool company Sonar‘s 2026 State of Code Developer Report, which surveyed more than 1,000 developers, states that 96% of developers have trouble trusting AI‑generated code. Further, 38% say reviewing AI‑generated code requires more effort than reviewing code written by colleagues. In the same report, “correcting or rewriting code created by AI coding tools” is listed as a top source of toil, especially among frequent AI users.
One of the Harvard report’s co-authors, Frank Nagle, Research Scientist at the Initiative on the Digital Economy at MIT, tells The New Stack that in “the current study, we did not drill into the quality of the code. But, anecdotally, I’ve heard similar things.” So, when people say they’re “coding” today, it’s not necessarily what we’d call coding only a few years ago.
Crucially, the researchers interpret this to mean that AI is not just a productivity bump, but a change in developers’ jobs. For maintainers and top contributors who keep high‑profile projects running, this rebalancing matters greatly. The study notes that these “power users” often spend a disproportionate share of their time on secondary tasks such as reviewing others’ contributions, merging code, and resolving user‑reported issues. That’s often a fast track to burnout.
Specifically, developers using Copilot saw their project‑management activity increase by nearly a quarter, while peer collaboration events decreased by almost 80%. Why? The authors think it’s because they needed to do less debugging and refactoring. That shift suggests that generative AI is acting as an always‑on reviewer and pair‑programmer, handling many of the small, routine fixes that previously would have required human intervention.
That’s good and bad news. While this relieves workload pressure, it also hints at a cultural risk for open source. Nagle warns in the paper of a “retreat away from teamwork” as developers lean on AI instead of colleagues for advice, design feedback, or code review. What has long distinguished open source is not just publicly visible code, but the dense web of human collaboration that shapes both software and developers.
While time‑saving is real, the loss of human interaction erodes the social and organizational value that companies and open-source communities derive from collaborative work. It appears that AI, by reducing peer contact, is another force hollowing out the human side of software engineering.
Another problem with this drastic decline in people working together is: “What happens when code changes flow with fewer human checkpoints?” Amazon has recently been showing us a real-world example of what happens: Nothing good. Due to numerous AI failures, Amazon is now requiring senior developers to oversee and approve the work of junior and mid-level AI-assisted programmers.
At the same time, the Harvard report found that the largest incremental benefits from generative AI appear among less‑experienced workers. Within the GitHub sample, lower-level developers using Copilot saw the largest increase in time spent on core coding activities. That said, as Nagle points out in The New Stack conversation, “Everyone in the sample is a maintainer, so even the lower-experienced people still have some higher level of experience than a total rookie.”
That said, in the paper, Nagle explicitly calls it a “profound strategic error” when companies cut junior hiring on the assumption that AI can fill the gap. The paper found that AI works best as a complement, accelerating skill development and preparing workers for higher‑level responsibilities. “When companies stop hiring entry‑level people, it’s short‑term thinking at the expense of investing in the future.”
Another result is that the Copilot-enabled developers increased their cumulative exposure to new languages by nearly 22% relative to baseline. This suggests that the tool enables low‑cost experimentation. Thus, AI is making it easier to try out a new language or framework because the AI can fill in idioms, boilerplate, and syntax on the fly.
What it all boils down to is that AI is clearly changing the very nature of programmers’ work. It also appears, though, that, just like AI itself, it’s still too early to say exactly what those changes will be. Strap in, folks, it’s going to continue to be a bumpy ride.
There is a special kind of annoyance that only Git seems capable of producing. You clean up a repo locally, get rid of the files you do not want, maybe tighten up the structure a bit so it actually looks like something worth keeping, and then you go to push it up to GitHub expecting a normal, uneventful success. Instead, Git throws a fit and tells you the remote contains work you do not have locally. Suddenly this simple little task turns into a standoff, and Git is acting like you are about...
Managing a WordPress site looks simple from the outside, but once you’re handling updates, security, performance, backups, and content every week, the workload adds up. Miss a task, and you risk slow load times, broken features, or security threats that reach your visitors before you notice something’s wrong.
That’s why you need a strong website management workflow. It keeps your site stable, protects your brand, and frees you up to focus on publishing, marketing, and growth.
In this guide, you’ll learn what WordPress website management includes, the tasks worth prioritizing, and the automation tools — like Jetpack and Automattic for Agencies — that help you maintain a fast, secure, reliable website with far less manual work.
What is WordPress website management?
WordPress website management is the ongoing work that keeps your site secure, fast, and running the way visitors expect. It includes updates, backups, performance checks, security scans, form testing, and content reviews. Even a small site needs regular attention because plugins change, new threats appear, and audience expectations keep rising.
Good WordPress maintenance protects the work you’ve already put in and gives you room to grow. When you keep an eye on performance, search visibility, and user behavior, you’re in a better position to refine content, publish with confidence, and catch issues before they cause serious harm.
Most modern workflows lean on automation to lighten the load. Jetpack handles tasks like backups, malware scanning, spam filtering, speed optimization, and social posting in the background. That support gives you a more reliable site, fewer late-night fixes, and more space to focus on bigger goals.
Essential WordPress site management checklist
A healthy WordPress site depends on steady, predictable upkeep. This checklist outlines the recurring tasks that keep everything secure, stable, and performing the way it should. Each item plays a different part, and together they create a solid plan to ensure long-term site health.
1. Site and database backups
Regular backups protect your work from accidents, server issues, plugin conflicts, and security threats. A complete backup includes your site files and your database so you can restore the entire site with minimal downtime. Cloud backups store files in a secure location separate from your site servers, giving you more options in an emergency and greater peace of mind.
2. Software updates for WordPress core, themes, and plugins
WordPress is always improving, and updates bring the latest innovations to your site. Applying updates for WordPress core, your active theme, and installed plugins reduces vulnerabilities and prevents compatibility issues. Scheduling time each week for updates — or automating them when appropriate — avoids long-term problems.
3. Security and malware scanning
Every site faces threats, whether from bots, vulnerabilities, or outdated code. Security scanning identifies suspicious activity, corrupted files, or signs of tampering and alerts you before bigger issues arise.
4. Activity and uptime monitoring
When your site goes offline, even briefly, you risk losing visitors, sales, and trust. According to a Calyptix/ITIC study, 37% of small-to-medium-sized businesses reported that just one hour of downtime costs between $1,000 and $5,000.
Uptime monitoring alerts you the moment your site becomes unavailable, while activity logs show who did what inside your dashboard. Together, they help you troubleshoot problems quickly and maintain a reliable online presence.
5. Form testing and optimization
Forms play a big role in conversions and lead generation, so they deserve regular check-ins. Test form submissions, make sure notifications arrive where they should, and confirm that integrations still work. With tools like Jetpack Forms, you can build and manage forms directly inside WordPress and monitor how well they perform over time.
6. Spam control
Spam comments, form submissions, and fake accounts waste your time and distort your site data. Automated spam filtering keeps junk out of your inbox and prevents bots from filling your database with useless noise.
7. Performance and speed tuning
Fast sites earn better search visibility, higher engagement, and stronger conversion rates. Performance tuning includes optimizing images, using caching tools, reducing unused scripts, and other optimizations targeting Core Web Vitals.
8. SEO health check and optimization
Search visibility relies on good structure, updated metadata, working links, clean sitemaps, and readable content. A periodic SEO review helps you identify what needs improvement. Small updates, like fixing broken links or adding structured data, add up to steady gains over time.
9. Content and social automation
A strong content workflow drives growth and cuts down on repetitive work. Automation lets you schedule posts, push updates to your social channels, and handle tasks like drafting or translation without bouncing between tools. When these pieces run in the background, you stay focused on strategy and publishing instead of micromanaging every step.
10. Analytics and visitor insights
Traffic, engagement, and user behavior tell you what’s working and what needs to change. Jetpack Stats offers quick, at-a-glance analytics right in your dashboard so you can track trends without navigating another tool.
11. Site search and discoverability
On-site search shapes how visitors explore your content. A tool like Jetpack Search upgrades the default WordPress search with faster results, filters, and relevancy sorting. Better search helps visitors find what they want, reduces bounce rates, and keeps people engaged longer.
Together, these tasks give you a complete picture of your site’s health.
How to automate WordPress management with the right tools
Automation takes a big chunk of the ongoing work out of running a WordPress site. Instead of checking backups, removing spam, running scans, or sharing posts one by one, tools monitor, update, and protect your site around the clock.
This results in fewer surprises, stronger performance, and more time to focus on content, marketing, or client work.
A strong automation setup handles the behind-the-scenes tasks that keep your site healthy while giving you a predictable, low-maintenance workflow. Jetpack brings many of these automations together in one tool, so you’re not stitching together a dozen unrelated plugins.
Here are a few ways to automate quickly and effectively:
Agency or freelancer? Explore Automattic for Agencies
If you manage multiple WordPress sites, automation becomes even more valuable. Automattic for Agencies gives you partner-level access to Jetpack tools, discounts on products you use across client sites, and a centralized way to manage and monitor your work.
You get a consistent stack for backups, security, performance, and publishing, which helps reduce manual upkeep and strengthen your services. You can even earn recurring commissions when you refer clients to key WordPress tools, hosting providers, and payment processors.
It’s how today’s leading agencies are getting ahead and creating more value from every client relationship.
Security: Auto-scan and auto-fix threats
Jetpack Scan monitors your site continuously, checking for malware, suspicious file changes, injected scripts, or anything that looks out of place. It checks both your core files and plugin directories, so you’re covered even when third-party tools introduce risks.
When it detects a known issue, it gives you a one-click fix that restores the affected files to a safe state. You can resolve the issue quickly, avoid downtime, and move on without sorting through code or running manual repairs.
Backups: Real-time, automated cloud backups
Jetpack Backup records every change the moment it happens, including new posts, theme edits, plugin updates, user actions, and more. Then, it stores those snapshots securely in the cloud. You get a complete, moment-by-moment history of your site instead of a single nightly backup that might miss important changes.
If something breaks after an update, a plugin conflict, or an accidental deletion, you can roll your site back to a precise point in time. This approach removes the stress of manual exports, outdated backup files, and recovery guesswork.
Performance: Automated speed and image optimization
Keeping a site fast takes ongoing work, especially as you add new content, plugins, or design elements. Jetpack Boost automates many of the tasks that normally require technical tuning. It generates Critical CSS so above-the-fold content appears sooner, defers nonessential JavaScript to speed up initial rendering, and optimizes how images load across your pages.
Together, these improvements create a smoother experience for visitors without requiring you to adjust code or manage multiple performance plugins.
Spam prevention: Intelligent spam filtering
Spam comments and bot-driven form submissions pile up quickly and drag down your workflow. They also skew analytics, clog your database, and make it harder to spot legitimate messages.
Jetpack Akismet Anti-Spam screens out junk automatically, blocking bots and low-quality submissions before they reach your dashboard. You spend less time moderating noise and more time reviewing the interactions that actually matter.
Content: Creation and translation
Jetpack AI Assistant helps you handle the heavy lifting of content creation right inside the WordPress editor. It can draft sections, rewrite paragraphs for clarity, expand ideas, or translate content when you need to reach a broader audience.
These tools help you move from outline to polished post much faster while still keeping full control over your tone, direction, and final message.
Social media: Auto-posting and scheduling
Jetpack Social pushes your new posts to your connected social channels automatically and gives you tools to schedule updates ahead of time.
You maintain a steady presence across multiple platforms without logging into each one or repeating the same steps every time you publish.
Frequently asked questions
How much does WordPress website management cost per month?
Costs vary depending on your site’s size, traffic, complexity, and whether you handle maintenance yourself or outsource it. For a basic DIY setup, you’re likely looking at around $30-$75 per month, covering backups, updates, and security.
As you add more automation tools, premium features or outsourcing, costs begin to climb. Many WordPress management services offer hands-off plans in the $150-$500/month range for small-to-medium business sites. For large or high-traffic sites, those numbers climb much higher.
What are the most common WordPress management mistakes to avoid?
Site owners often skip updates, don’t keep current backups, ignore security warnings, install too many plugins, or rely on inexpensive hosting that slows everything down. Another common issue is not testing contact forms or checkout flows, which can cause missed leads or lost revenue. Setting up a recurring checklist and using automation tools helps you avoid these gaps.
Do I need coding skills to manage a WordPress site?
No, most management tasks like updates, backups, spam filtering, or performance checks don’t require coding at all. Modern tools like Jetpack handle the technical tasks. Coding becomes helpful only if you want custom features, advanced design changes, or troubleshooting complex errors.
How do I back up my WordPress site automatically?
You can automate backups with tools like Jetpack VaultPress Backup, which captures changes in real time and stores them in the cloud. Once activated, backups run continuously in the background. If you ever need to restore your site, you can roll back to a specific moment without manual file handling.
What is WordPress malware scanning and why is it important to automate?
Malware scanning checks your files and database for suspicious changes, injected code, or harmful activity. Automated scanning ensures threats are caught as soon as they appear instead of waiting for you to run a manual check. A tool like Jetpack Scan also offers one-click fixes for known issues, which helps you recover quickly and reduce downtime.
What is the easiest way to prevent spam comments on WordPress?
The fastest and most reliable approach is automated spam filtering. Jetpack Anti-Spam blocks bot submissions, fake comments, and junk form entries before they reach your dashboard. It protects your site’s performance, keeps your database clean, and saves you from sorting through piles of useless notifications.
How can I easily speed up my WordPress website without coding?
You can improve performance with automated image optimization, page caching, script deferral, and Critical CSS generation. Jetpack Boost handles these tasks for you so your site loads faster without requiring code edits or plugin stacking.
Can AI help with WordPress content management?
Yes, tools like Jetpack AI Assistant help with planning, drafting, rewriting, and translating content inside the editor. They speed up your workflow while keeping you in control of the final tone and message. AI also assists with automating alt text, simplifying content updates, and supporting multi-language publishing.
Can I manage multiple WordPress sites easily?
Yes, you can manage multiple WordPress sites easily, especially with the right tools and structure. Using Jetpack across your sites gives you consistent backups, security tools, performance optimization, and analytics. Agencies can simplify this even further by joining Automattic for Agencies, which provides partner pricing, centralized project management for multiple sites, and access to scalable workflows.
What plugins should beginners install first for site management?
Most beginners start with a small but reliable toolkit: a backup plugin, a security scanner, a performance optimizer, an anti-spam tool, and a simple analytics solution. Jetpack bundles all of these into separate modules, making it straightforward to activate exactly what you need as your site grows.
Tech talks are a new blog post series where we share glimpses into our work on Electron. If you find this work interesting, please consider contributing!
When Electron switched to Wayland on Linux last fall, most people didn't notice.
Major Linux distributions adopted the modern display protocol years ago, and both the KDE Plasma and GNOME desktop environments are in the process of dropping X11 supportcompletely.
But a platform migration isn't complete without apps, and a large part of the Linux app ecosystem went through a second Wayland transition last August — well after most distros had changed their defaults. That's when Chromium turned on Wayland by default, bringing Electron and dozens of Linux desktop apps along with it.
Wayland is supported out of the box in Electron 38.2 and newer. As long as your apps are up-to-date, it just works. (If you were previously launching your Electron apps with very long commands like CONFUSING_OZONE_VARIABLE --ozone-platform=wayland, you no longer need to do that.)
This change was possible because the Chromium and Electron projects have been working on Wayland support for more than half a decade. But until recently, Chrome and Electron apps continued to use X11 by default, even when launched in a Wayland session. This wasn’t a big issue, since X11 apps still work fairly well on Wayland by running inside an invisible X server called Xwayland.
Running apps through a compatibility layer is not the same as running them directly on Wayland. On Wayland, there’s less sitting between your app and the compositor, so there's lower overhead and much stronger isolation between applications. Modern Wayland compositors also let apps take advantage of newer platform and display features like variable refresh rates, HiDPI and fractional scaling, and HDR.
These are all good reasons for Electron to make the switch. In late September, Electron followed Chromium’s lead and began defaulting to Wayland. And as apps began to update, people who had been “using Wayland” without issues for months or years started to find out what it was really like to experience their apps on Wayland for the first time.
Supporting Wayland required dozens of changes throughout Chromium and Electron, from internals to developer-facing APIs. It also required a different way of thinking about what desktop apps should be able to do.
Wayland reconsiders assumptions made by older systems and asks whether apps should be able to:
Take focus away from other apps
View and interact with windows from other apps
Respond to mouse and keyboard input when not focused
Choose where to position their own windows on the screen (and which physical monitor to appear on)
Resize their windows at any time
Wayland's answer to these questions is essentially “no.” When you open a window, the compositor — not the app developer — decides where it goes. Apps cannot unilaterally move, resize, or focus their windows without user input, and they can only interact with the rest of the desktop through optional protocol extensions and XDG portals.
These kinds of rules are understandable; no one likes it when a misbehaving app steals focus or loads halfway off the screen. But it can still surprise people when their apps suddenly lose access to familiar affordances on Wayland. This is especially the case for a cross-platform framework like Electron, which exists to help developers achieve consistent results everywhere.
Other features work differently: recording the screen with desktopCapturer and setting keyboard shortcuts with globalShortcut are more restricted, and both heavily depend on the desktop environment and portal versions. Here's what it looks like when screen sharing in Signal Desktop on GNOME 48.
Making this more complicated for developers is the fact that Wayland isn't a single piece of software, but a protocol. Every compositor implements it a little differently, almost like browser engines. (There are even protocol support trackers that look like they came from MDN or CanIUse.)
So when Slack tries to focus its main window with win.focus(), GNOME's compositor (Mutter) shows a notification. On KDE Plasma (KWin), the app icon flashes in the panel instead. Neither outcome is what the app's developers had in mind, but both are valid interpretations of the activation spec.
Some capabilities simply work better on Wayland than on X11, including anything to do with colors, transparency, and hardware-accelerated rendering. win.setOpacity(n) is an example of an Electron API which hasn't been available on Linux in the past, but which will now be feasible to support.
Even the stricter restrictions can benefit apps. When 1Password runs on Wayland, its SSH agent lets users confirm requests with a single click instead of asking them to enter their passwords. This is safe because Wayland's input isolation is strong enough to prevent the prompt from being skipped with clickjacking — only a real human being can click the button.
The basic tradeoff is that Wayland restricts some of what apps can do but also enables them to be more capable and secure. And in one area, Wayland gives developers more flexibility and more responsibility than before: client-side decorations (CSD).
Understanding CSD, or when a window isn’t a window
The Wayland protocol is very lightweight, and its simplicity extends to the way it draws window frames. On X11, the window manager typically supplies a window’s title bar and frame decorations. But when you create a window (xdg_toplevel) on Wayland, all you get back from the compositor is a plain rectangle.
That rectangle is a powerful canvas. On a modern compositor like GNOME’s Mutter, it’s triple-buffered and GPU-accelerated. But if you want any of the trimmings users might expect — title bar buttons, drop shadows, even resize handles — you have to add them yourself. This requirement is called client-side decorations (CSD), and it’s one of the major differences between X11 and Wayland.
Electron already had some support for client-side decorations, provided by a class called ClientFrameViewLinux which uses GTK to paint convincing native window frames. These look very similar to the ones GNOME used to supply on X11, but they are produced entirely in-framework.
But client-side window frames are not an exact match for server-side decorations (SSD) from X11 window managers. They need to be implemented by each app or framework, so the details can look noticeably different when you put apps side by side, from their title bar areas right down to their drop shadows and corner shapes.
The differences are usually minor, but when CSD is completely absent from a window, the result can be visually jarring.
Many popular apps, including Visual Studio Code, Obsidian, and Discord, use frameless windows with custom title bars. Prior to Electron 41, frameless windows did not support CSD at all, so they looked like featureless rectangles on Wayland.
Improving coverage for CSD was a task with framework-wide consequences. The biggest obstacle involved window sizes and how to measure and set them accurately. Electron already manages two different kinds of window boundaries:
“window bounds”, the size of the window, including its titlebar, menubar, and frame.
“content bounds”, the size of the internal web view which hosts the app’s web content.
Both values can be controlled independently. If a developer calls for an 800x600 window, Electron calculates the height of the title bar and shrinks the web app to something like 800x540. (It also works the other way around for content-sized windows.)
To support CSD, Electron also needed to keep track of a new kind of boundary:
“widget bounds”, the size of the transparent widget which draws everything inside of it, including the window frame and its external decorations.
When CSD is required, Electron first takes the window's underlying surface (accessed internally via a Chromium accelerated widget) and inflates it so it's large enough to fit all the decorations.
The framework then paints the opaque bits of the window (title bar, frame, and web content) at their appropriate sizes and positions inside the transparent widget. The outermost areas are filled in with drop shadows and resize hit targets, creating the look and feel of a native, three-dimensional window without relying on server-side decorations.
With CSD, a "logical" window at 800x600 might be inset into a 840x640 widget. The exact geometries depend on the user's theme and the window's state: whether it is currently active, maximized, tiled, or fullscreen can affect the size and presence of decorations.
Of course, widget bounds should never leak into the public API. The framework needs to abstract this complexity away from app developers, who are generally not thinking about the extents of resize targets or shadow insets changing underneath them.
The good news is that much of this was sorted out between last September and March, and as a result, Electron 41 supports CSD on Wayland in all window configurations, including frameless windows with Window Controls Overlay.
Wayland is an everyday reality for Linux users in 2026, so a great Wayland experience is now just what it means to support Linux.
Electron reached an important milestone last month with the creation of a Wayland test job in CI. More tests still need to be ported over, but it’s now much easier to catch regressions.
Now that the basic support is in place, Wayland opens up new possibilities for Electron apps. CSD in particular offers developers more ways to customize window frames and integrate them with both their web content and the platform. Let us know what you'd like to see; one feature that's high on my own shortlist is rounded corners.
The framework is only part of the story. If you develop an Electron app and you haven’t thoroughly tested it on Linux in a while (even as recently as last fall), give it a spin with Electron 41+ on a modern distribution like Ubuntu 25.10 or Fedora 43. Try your app on both KDE Plasma and GNOME, and maybe something more exotic like Niri.
You may discover changes you could make to accommodate Wayland's unique constraints. Some differences are covered in the Electron documentation, but the best way to understand the new environment is to use it.
And if you’d like to see faster progress and support for more platform features, consider becoming a contributor. Like Linux itself, Electron is a community-run free software project that’s open to everyone, and we're actively looking for Linux contributors and maintainers.
Electron powers many of the most popular desktop apps across platforms, so getting involved is an effective way to help make desktop Linux more viable for millions of people.
Log in
