Blog / Operating systems & apps /

Electron apps: why some desktop apps feel slow

Open your task manager and sort by memory. Chances are a chat app, a code editor or a note-taking tool is near the top, using more RAM than seems reasonable for what it does.

There’s a good chance it’s built on Electron. That doesn’t make it a bad app. It does explain the weight, and it explains a trade-off I think is mostly fair, even if I understand why people grumble.

The argument

My view: Electron apps are heavier than they need to be, and that’s a real cost you pay. But the alternative for many teams is no desktop app, or a worse one, so the weight is often the price of getting the software at all. Users should expect more efficiency; developers should be honest about the cost; and the answer isn’t to ban the approach.

What Electron is

Electron is a framework that lets developers build desktop apps using web technology: HTML, CSS and JavaScript. Under the bonnet, every Electron app bundles two big pieces:

  1. Chromium, the open-source engine behind Chrome, to draw the interface.
  2. Node.js, to handle things outside the browser, like files on your computer.

So an Electron app is, loosely, a private copy of a web browser wearing the app’s name, running a web page. Apps you probably recognise as Electron-based include Slack, Discord, Visual Studio Code and Notion’s desktop app.

Imagine every app arriving with its own engine, in the way a food truck brings its own kitchen. Efficient for the truck owner, wasteful if ten food trucks park on your street.

Why they feel slow

  1. Each app carries its own browser. Run several Electron apps and you’re running several copies of Chromium. Each one uses memory.
  2. Web interfaces aren’t always lean. A page built with layers of scripts can use a lot of memory and CPU, especially if it stays open all day.
  3. Startup cost. The engine has to load before the app does. That’s why some apps take a moment to appear.
  4. Memory isn’t always released. Long-running sessions can creep upward, and sloppy code makes it worse.
  5. They sit in the background. Chat apps keep running to stay connected. They often launch at login, too.

Not every Electron app is heavy, and not every heavy app is Electron. Well-built Electron apps can be quick and polished. Badly built native apps can be slow. VS Code, for instance, is Electron-based and widely considered fast for what it does, because its team put in serious effort on performance.

Why developers choose it

This matters for the fair-minded answer.

  • One codebase for Windows, Mac and Linux. A small team can ship on all three. Building three native apps costs far more.
  • Web skills transfer. Developers who know JavaScript can build desktop software without learning new languages.
  • Speed of building. Interface changes can be made and shipped quickly.
  • A big ecosystem of libraries already exists.

Without that, a lot of tools you use simply wouldn’t have a desktop version, or would arrive years later. That’s a real benefit to users. I looked at a related trade-off in cross-platform apps vs native apps.

The strongest counter-argument

“Computers have lots of RAM now, so who cares?” is the usual defence. It’s weak. Many people use laptops with 8 GB, shared among a browser with a dozen tabs, a video call and a chat app. An app that insists on a gigabyte on its own is taking a share of a limited pool. And in markets where an affordable laptop has modest specs, the cost is higher. “Buy more RAM” is advice that assumes a certain budget.

The opposite argument, “all Electron apps are bloated rubbish”, is also too simple. The engine isn’t the only factor, and some of the best-loved tools on the desktop use it.

My position is in between. Electron is a practical tool that gets software built. It has a cost, and that cost should be tracked and reduced, not ignored.

Alternatives

  • Native apps, built with the operating system’s own tools. Usually the lightest and most integrated, but expensive to build for several platforms.
  • Tauri and similar frameworks, which use the system’s built-in web view rather than bundling a browser. They produce much smaller apps, though they depend on the web view each platform provides, which brings its own differences.
  • Progressive web apps, which run in your browser and can be installed like an app. They share the browser’s engine, so you don’t pay the cost of a second copy. I explained them in progressive web apps explained.
  • Just use the website. For many chat and note tools, the browser version is nearly as good, and you already have one browser open.

What you can do as a user

  1. Check which apps use the most memory in Task Manager (Windows) or Activity Monitor (Mac), and see whether you need them running.
  2. Stop apps launching at startup if you rarely use them.
  3. Quit apps rather than leaving them open all week. Restarting frees leaked memory.
  4. Use the web version of apps you only open occasionally.
  5. Keep apps updated. Updates often include memory fixes.
  6. Consider more RAM if you can add it. For many laptops it’s not possible, but on those where it is, it’s a cheap fix.

What this means if you build for the web

If you make websites or web apps, the Electron story is a reminder: everything you ship runs on someone’s real computer. Heavy JavaScript, big images and background scripts cost memory and battery, not just load time. I’ve written elsewhere about JavaScript SEO basics for site owners, and the same discipline applies. Lean pages and lean apps are respectful.

Key takeaways

  • Electron apps bundle a browser engine, which is why they use extra memory.
  • The cost is real, but so is the benefit: more software on more platforms.
  • Careful engineering makes a big difference; the framework isn’t a sentence.
  • You can reduce the pain by managing startup apps and using web versions.

FAQ

How do I know if an app is built with Electron?

Sometimes the developer says so. Often, the process list shows a name like the app followed by several helper processes. A quick search for the app’s name plus “Electron” usually settles it.

Is Electron insecure?

It can be if built carelessly, as any software can. Follow the developer’s updates.

Will Electron go away?

Unlikely soon. Alternatives are growing, but plenty of teams depend on it.

Which app on your computer uses more memory than you think it should, and would you swap it for a lighter one?