--- description: Electron or Tauri for your Capacitor desktop app? Compare binary size, plugin support, security, and Live Updates to choose the right platform. title: Electron vs. Tauri for Capacitor Apps - Capawesome image: https://capawesome.io/docs/assets/images/social/blog/electron-vs-tauri-for-capacitor-apps.png --- [Skip to content ](#electron-vs-tauri-for-capacitor-apps) [🖥️ Introducing the **Capacitor Electron Platform** — build desktop apps for macOS, Windows, and Linux. Free & open source. ](/blog/announcing-the-capacitor-electron-platform/) * [ SDKs ](/docs/sdks/) * [ Formbricks ](/docs/sdks/capacitor/formbricks/) * [ Geocoder ](/docs/sdks/capacitor/geocoder/) * [ Google Sign-In ](/docs/sdks/capacitor/google-sign-in/) * [ Grafana Faro ](/docs/sdks/capacitor/grafana-faro/) * [ Gyroscope ](/docs/sdks/capacitor/gyroscope/) * [ Haptics ](/docs/sdks/capacitor/haptics/) * [ Home Indicator ](/docs/sdks/capacitor/home-indicator/) * [ In-App Browser ](/docs/sdks/capacitor/in-app-browser/) * [ Install Referrer ](/docs/sdks/capacitor/install-referrer/) * [ Intercom ](/docs/sdks/capacitor/intercom/) * [ Intune ](/docs/sdks/capacitor/intune/) * [ Keep Awake ](/docs/sdks/capacitor/keep-awake/) * [ libSQL ](/docs/sdks/capacitor/libsql/) * [ Light Sensor ](/docs/sdks/capacitor/light-sensor/) * [ Live Update ](/docs/sdks/capacitor/live-update/) * [ Localization ](/docs/sdks/capacitor/localization/) * [ Mail Composer ](/docs/sdks/capacitor/mail-composer/) * [ Managed Configurations ](/docs/sdks/capacitor/managed-configurations/) * [ Maps Launcher ](/docs/sdks/capacitor/maps-launcher/) * [ Media Session ](/docs/sdks/capacitor/media-session/) * [ ML Kit ](/docs/sdks/capacitor/mlkit/) * [ Navigation Bar ](/docs/sdks/capacitor/navigation-bar/) * [ Network ](/docs/sdks/capacitor/network/) * [ NFC ](/docs/sdks/capacitor/nfc/) * [ Node.js ](/docs/sdks/capacitor/nodejs/) * [ OAuth ](/docs/sdks/capacitor/oauth/) * [ Passkeys ](/docs/sdks/capacitor/passkeys/) * [ Password Autofill ](/docs/sdks/capacitor/password-autofill/) * [ PDF Generator ](/docs/sdks/capacitor/pdf-generator/) * [ PDF Viewer ](/docs/sdks/capacitor/pdf-viewer/) * [ Pedometer ](/docs/sdks/capacitor/pedometer/) * [ Permissions ](/docs/sdks/capacitor/permissions/) * [ Phone Dialer ](/docs/sdks/capacitor/phone-dialer/) * [ Photo Editor ](/docs/sdks/capacitor/photo-editor/) * [ Photo Manipulator ](/docs/sdks/capacitor/photo-manipulator/) * [ PixLive ](/docs/sdks/capacitor/pixlive/) * [ PostHog ](/docs/sdks/capacitor/posthog/) * [ Printer ](/docs/sdks/capacitor/printer/) * [ Privacy Screen ](/docs/sdks/capacitor/privacy-screen/) * [ Proximity Sensor ](/docs/sdks/capacitor/proximity-sensor/) * [ Purchases ](/docs/sdks/capacitor/purchases/) * [ RealtimeKit ](/docs/sdks/capacitor/realtimekit/) * [ Root Detection ](/docs/sdks/capacitor/root-detection/) * [ Screen Brightness ](/docs/sdks/capacitor/screen-brightness/) * [ Screen Orientation ](/docs/sdks/capacitor/screen-orientation/) * [ Screen Reader ](/docs/sdks/capacitor/screen-reader/) * [ Screenshot ](/docs/sdks/capacitor/screenshot/) * [ Secure Preferences ](/docs/sdks/capacitor/secure-preferences/) * [ Settings Launcher ](/docs/sdks/capacitor/settings-launcher/) * [ Shake ](/docs/sdks/capacitor/shake/) * [ Silent Mode ](/docs/sdks/capacitor/silent-mode/) * [ SIM ](/docs/sdks/capacitor/sim/) * [ SMS Composer ](/docs/sdks/capacitor/sms-composer/) * [ Speech Recognition ](/docs/sdks/capacitor/speech-recognition/) * [ Speech Synthesis ](/docs/sdks/capacitor/speech-synthesis/) * [ Share Target ](/docs/sdks/capacitor/share-target/) * [ Square Mobile Payments ](/docs/sdks/capacitor/square-mobile-payments/) * [ SQLite ](/docs/sdks/capacitor/sqlite/) * [ Superwall ](/docs/sdks/capacitor/superwall/) * [ System WebView ](/docs/sdks/capacitor/system-webview/) * [ Tauri ](/docs/sdks/capacitor/tauri/) * [ Text Interaction ](/docs/sdks/capacitor/text-interaction/) * [ Text Zoom ](/docs/sdks/capacitor/text-zoom/) * [ Thermal State ](/docs/sdks/capacitor/thermal-state/) * [ Toast ](/docs/sdks/capacitor/toast/) * [ Torch ](/docs/sdks/capacitor/torch/) * [ Vault ](/docs/sdks/capacitor/vault/) * [ Volume ](/docs/sdks/capacitor/volume/) * [ Wallet ](/docs/sdks/capacitor/wallet/) * [ Wifi ](/docs/sdks/capacitor/wifi/) * [ YouTube Player ](/docs/sdks/capacitor/youtube-player/) * [ Zip ](/docs/sdks/capacitor/zip/) * [ Cordova ](/docs/sdks/cordova/) * [ Cloud ](/docs/cloud/) * [ Integrations ](/docs/cloud/live-updates/integrations/) * Concepts * Reference * [ Troubleshooting ](/docs/cloud/live-updates/troubleshooting/) * [ FAQ ](/docs/cloud/live-updates/faq/) * [ Native Builds ](/docs/cloud/native-builds/) * [ Set Up Environments ](/docs/cloud/native-builds/environments/) * [ Overwrite Native Configurations ](/docs/cloud/native-builds/native-configurations/) * [ Auto-Increment Build Numbers ](/docs/cloud/native-builds/auto-incrementing-build-numbers/) * [ Configure the Web Build Script ](/docs/cloud/native-builds/web-build-script/) * [ Build from a Monorepo ](/docs/cloud/native-builds/monorepo/) * [ Use pnpm, Yarn, or bun ](/docs/cloud/native-builds/package-managers/) * [ Install Private npm Packages ](/docs/cloud/native-builds/npm-private-registry/) * [ Override the Java Version ](/docs/cloud/native-builds/override-java-version/) * [ Custom iOS Provisioning Profiles ](/docs/cloud/native-builds/custom-ios-provisioning-profiles/) * [ Build without Git ](/docs/cloud/native-builds/build-without-git/) * [ Access Git Behind a Firewall ](/docs/cloud/native-builds/firewall-access/) * [ Integrations ](/docs/cloud/native-builds/integrations/) * Reference * [ Troubleshooting ](/docs/cloud/native-builds/troubleshooting/) * [ FAQ ](/docs/cloud/native-builds/faq/) * [ App Store Publishing ](/docs/cloud/app-store-publishing/) * [ Submit a Build ](/docs/cloud/app-store-publishing/submit-a-build/) * [ Submit Automatically After a Build ](/docs/cloud/app-store-publishing/submit-automatically/) * [ Troubleshooting ](/docs/cloud/app-store-publishing/troubleshooting/) * [ FAQ ](/docs/cloud/app-store-publishing/faq/) * [ Automations ](/docs/cloud/automations/) * [ Reference ](/docs/cloud/automations/reference/) * [ Troubleshooting ](/docs/cloud/automations/troubleshooting/) * [ FAQ ](/docs/cloud/automations/faq/) * [ Assist ](/docs/cloud/assist/) * [ CLI ](/docs/cloud/cli/) * APIs and SDKs * [ Webhooks ](/docs/cloud/webhooks/) * [ Integrations ](/docs/cloud/integrations/) * Account * [ Organization ](/docs/cloud/organizations/) * [ Two-Factor Enforcement ](/docs/cloud/organizations/two-factor-authentication/) * [ Audit Logs ](/docs/cloud/organizations/audit-logs/) * [ Billing ](/docs/cloud/organizations/billing/) * [ License Keys ](/docs/cloud/license-keys/) * [ AI ](/docs/ai/) * [ Insiders ](/docs/insiders/) * [ Billing & Plans ](/docs/insiders/billing-and-plans/) * [ FAQ ](/docs/insiders/faq/) * [ License ](https://capawesome.io/legal/eula/) * [ Support ](/docs/support/) * [ Contributing ](/docs/contributing/) * Contributing code * [ Code of Conduct ](/docs/contributing/code-of-conduct/) * [ Questions ](https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion#creating-a-discussion) * [ Blog ](/blog/) * Categories * [ Stay in the loop ](#stay-in-the-loop) * [ Conclusion ](#conclusion) * Related links # Electron vs. Tauri for Capacitor Apps[¶](#electron-vs-tauri-for-capacitor-apps "Permanent link") Capawesome now offers two ways to take a Capacitor app to the desktop: the [Capacitor Electron Platform](/docs/sdks/capacitor/electron/) and the [Capacitor Tauri Platform](/docs/sdks/capacitor/tauri/). Both are open source, both run your existing web build on macOS, Windows, and Linux, and both are maintained by the same team. So the question of Electron vs. Tauri for Capacitor apps is not about which project is better in the abstract. It is about which one fits the app you are building. This post walks through that decision. [ ![Build and deploy your Capacitor app with Capawesome Cloud](https://capawesome.io/assets/banners/cloud-build-and-deploy-capacitor-apps.png?t=1) ](https://capawesome.io/) **Key takeaways:** * The Capacitor Electron platform bundles Chromium and Node.js, which means larger installers (\~80–150 MB) but the widest plugin support and web-bundle Live Updates. * The Capacitor Tauri platform ships a tiny binary (\~3–10 MB) by reusing the system webview and running a Rust core with deny-by-default permissions. * Electron is the first Capacitor desktop platform with web-bundle over-the-air Live Updates. Tauri compiles web assets into the binary, so it supports only full signed binary updates. * Tauri does not run arbitrary native Capacitor plugins. It supports a curated set plus web-implementation fallback, because there is no Node.js runtime. * Electron needs only npm. Tauri additionally requires the Rust toolchain and platform system dependencies. * Both are MIT licensed, target macOS, Windows, and Linux, and report `isNativePlatform()` as `true`. ## Electron vs. Tauri: which should you choose?[¶](#electron-vs-tauri-which-should-you-choose "Permanent link") Choose Electron if you need broad plugin support, over-the-air Live Updates, or the simplest possible setup. Choose Tauri if binary size, memory footprint, and a hardened security model matter more than plugin breadth, and your app can work with web plus a curated set of plugins. Both platforms run the same Capacitor web build, so most application code stays identical between them. The table below summarizes the practical differences. | Aspect | Capacitor Electron | Capacitor Tauri | | ----------------------- | ---------------------------------- | ------------------------------------------------- | | Binary size | \~80–150 MB | \~3–10 MB | | Webview | Bundled Chromium | System webview (WKWebView / WebView2 / WebKitGTK) | | Runtime / language | Node.js | Rust core | | Plugin support | Any Electron or web implementation | Built-in + curated + web only | | Web-bundle Live Updates | Available | Not available | | Dev toolchain | npm only | Rust toolchain required | | Version floor | Capacitor 6+ / Electron 28+ | Capacitor 8+ / Tauri 2+ | ## Binary size and memory[¶](#binary-size-and-memory "Permanent link") Tauri ships the operating system's own webview, so installers land in the \~3–10 MB range and memory use stays modest. Electron bundles a full copy of Chromium and Node.js with every app, which puts installers around \~80–150 MB and gives each process a heavier baseline memory footprint. For a menu-bar utility, a kiosk build, or a consumer app that users download over a metered connection, that size gap is noticeable. For an internal tool or a data-heavy line-of-business app where a hundred megabytes is a rounding error next to the value delivered, it rarely changes the decision. Be honest about which category your app falls into before you let size drive the choice. Memory follows a similar pattern. Because Electron runs its own Chromium and a Node.js main process, idle memory sits higher than a comparable Tauri app that leans on the system webview. On a modern developer machine you may not feel it, but on low-end hardware, on a Raspberry Pi running a kiosk, or on a fleet of older office PCs, the difference adds up. Size and memory tend to point in the same direction, so if one of them is a hard constraint for your deployment target, treat it as a strong signal toward Tauri. ## Plugin support[¶](#plugin-support "Permanent link") Plugin support is the single most decisive factor between the two platforms, so it is worth understanding in detail. The Capacitor Electron platform runs on Node.js. That means any Capacitor plugin with an Electron implementation works, and any plugin that ships a web implementation falls back to it automatically. In practice this covers a very large share of the ecosystem, and you can write your own Electron-side code when a plugin needs native desktop behavior. The Capacitor Tauri platform has no Node.js runtime, so its plugin story has exactly three tiers: * **Built-in.** `@capacitor/app` is supported directly by the platform. * **Curated crates.** A hand-picked set of plugins is wired up through official `tauri-plugin-*` crates, currently `@capacitor/filesystem`, `@capacitor/preferences`, `@capacitor/dialog`, and `@capacitor/local-notifications`. * **Web fallback.** Any plugin with a web implementation runs through the webview. Anything outside those tiers does not work. Arbitrary native Capacitor plugins will not run on Tauri, because there is no Node.js layer for them to execute in. If your app depends on a specific native plugin that only ships iOS, Android, and Electron implementations, that alone points you to Electron. The practical way to make this call is to audit your dependencies before you commit. List every Capacitor plugin your app uses, then check each one against the three Tauri tiers. If everything you need is either built in, on the curated list, or has a web implementation you are happy with, Tauri stays on the table. The moment one required plugin needs genuine native desktop code that only exists as an Electron implementation, the decision is effectively made for you. This audit takes a few minutes and saves you from discovering a hard blocker halfway through a Tauri build. ## Live Updates and over-the-air updates[¶](#live-updates-and-over-the-air-updates "Permanent link") The Capacitor Electron platform is the first Capacitor desktop platform to support web-bundle [Live Updates](/docs/cloud/live-updates/). Because Electron loads your web assets from disk at runtime, a new web bundle can be delivered over the air, with a provider-agnostic serving API and automatic rollback if a bundle fails to boot. Tauri works differently. It compiles your web assets directly into the application binary during the build, so there is no separate web bundle to swap at runtime. Updates on Tauri are full signed binary updates delivered through `tauri-plugin-updater`. That is a perfectly good update mechanism, but it is not the same as pushing a small web-only patch to users in minutes. This distinction has real consequences for how you ship. With Electron and Live Updates, you can fix a bug in your web layer, publish a new bundle, and have users on the fix within minutes, without waiting on app store review or asking anyone to re-download an installer. Failed boots roll back automatically, so a bad bundle does not brick the app. With Tauri, every change ships as a new binary that users download and install, which is slower to roll out and heavier to distribute. Neither approach is wrong; they suit different release cadences. If over-the-air updates of your web layer are part of your release strategy, choose Electron. ## Security model[¶](#security-model "Permanent link") The Capacitor Electron platform is secure by default. It enables a sandboxed renderer, context isolation, a strict content security policy, and validated IPC out of the box, and these defaults are not configurable. You get a hardened baseline without having to assemble it yourself. Tauri approaches security from the Rust side. Its core runs with deny-by-default permissions, and the build generates capability files that grant only the specific permissions the plugins you actually enabled require. Nothing is exposed to the web layer unless you have opted into it. For security-sensitive apps, that explicit, minimal-grant model is a strong argument. Both models are solid. The difference is philosophy: Electron gives you a fixed hardened default, while Tauri gives you a granular permission system you shape per app. ## Webview consistency[¶](#webview-consistency "Permanent link") Electron bundles one specific version of Chromium and ships it with every build. Rendering behaves the same on macOS, Windows, and Linux, and it stays the same until you update the platform. For teams that value predictable output and fewer surprises in CSS and JavaScript behavior, that consistency is valuable. Tauri relies on three different system webview engines: WKWebView on macOS, WebView2 on Windows, and WebKitGTK on Linux. These engines are at different versions and behave differently, so a layout or API that works on one may need attention on another. This is a real cross-engine testing burden, and it tends to be worst on Linux, where WebKitGTK lags behind. Budget for that testing if you go with Tauri. ## Developer setup[¶](#developer-setup "Permanent link") Setup effort differs too. The Capacitor Electron platform needs only npm, so if you already have a Capacitor project running you can add the desktop target with the tooling you have. The Capacitor Tauri platform additionally requires the Rust toolchain and the platform-specific system dependencies that Tauri 2 needs to build. This is a one-time cost per developer machine and per CI runner, but it is a cost. If your team has no Rust experience and wants the shortest path to a desktop build, Electron will feel lighter. ## When should you choose Electron?[¶](#when-should-you-choose-electron "Permanent link") Electron is the right call when: * Your app depends on native plugins with Electron implementations, or on a wide range of plugins in general. * You want to ship web-bundle Live Updates and push over-the-air patches to desktop users. * You want the simplest setup with npm only and no extra toolchain. * Predictable, consistent rendering across all three operating systems matters to you. * Installer size and memory footprint are not primary constraints for your audience. ## When should you choose Tauri?[¶](#when-should-you-choose-tauri "Permanent link") Tauri is the better fit when: * You want a lean binary for a consumer, kiosk, or utility app where download size and memory matter. * Security is a priority and you want a deny-by-default permission model with minimal grants. * Your app works well with web implementations plus the curated set of supported plugins. * You do not need over-the-air updates of your web layer and are comfortable shipping full signed binary updates. * Your team can absorb the Rust toolchain requirement and the cross-engine webview testing that comes with system webviews. ## FAQ[¶](#faq "Permanent link") ### Is Tauri smaller than Electron?[¶](#is-tauri-smaller-than-electron "Permanent link") Yes, by a wide margin. A Capacitor Tauri build produces installers in the \~3–10 MB range because it reuses the system webview, while a Capacitor Electron build lands around \~80–150 MB because it bundles Chromium and Node.js. ### Can I use any Capacitor plugin with Tauri?[¶](#can-i-use-any-capacitor-plugin-with-tauri "Permanent link") No. The Capacitor Tauri platform supports three tiers only: `@capacitor/app` built-in, a curated set of plugins on official `tauri-plugin-*` crates (`@capacitor/filesystem`, `@capacitor/preferences`, `@capacitor/dialog`, `@capacitor/local-notifications`), and any plugin with a web implementation. Arbitrary native plugins do not run, because there is no Node.js runtime. The Capacitor Electron platform, by contrast, supports any plugin with an Electron or web implementation. ### Which one supports Live Updates?[¶](#which-one-supports-live-updates "Permanent link") Electron. The Capacitor Electron platform is the first Capacitor desktop platform with web-bundle Live Updates. Tauri compiles web assets into the binary and supports only full signed binary updates. ### Do both support macOS, Windows, and Linux?[¶](#do-both-support-macos-windows-and-linux "Permanent link") Yes. Both platforms target macOS, Windows, and Linux, and both report `isNativePlatform()` as `true`. ### What does `Capacitor.getPlatform()` return on each?[¶](#what-does-capacitorgetplatform-return-on-each "Permanent link") It returns `'electron'` on the Capacitor Electron platform and `'tauri'` on the Capacitor Tauri platform, so you can branch on the desktop runtime at runtime. ## Stay in the loop[¶](#stay-in-the-loop "Permanent link") Both desktop platforms are moving quickly, and the plugin support tiers and Live Update capabilities keep expanding. Subscribe to the newsletter to hear about new releases first. [Subscribe to the Capawesome Newsletter](https://capawesome.io/newsletter) ## Conclusion[¶](#conclusion "Permanent link") The decision comes down to a few clear trade-offs. Pick Electron for broad plugin support, over-the-air Live Updates, predictable rendering, and the simplest npm-only setup, at the cost of a larger binary. Pick Tauri for a tiny binary, a low memory footprint, and a granular Rust security model, as long as your app fits the curated-plus-web plugin story and does not need to update its web layer over the air. Because both run the same Capacitor web build, you can even prototype against one and switch later without rewriting your app. If you want to see the Electron path end to end, read [Build a desktop app with Capacitor and Electron](/blog/how-to-build-a-desktop-app-with-capacitor-and-electron/). For questions, join the [Capawesome Discord server](https://discord.gg/VCXxSVjefW), and subscribe to the [Capawesome newsletter](https://capawesome.io/newsletter) to stay up to date. July 17, 2026 Back to top ```json { "@context": "https://schema.org", "@type": "BlogPosting", "headline": "Electron vs. Tauri for Capacitor Apps", "description": "Electron or Tauri for your Capacitor desktop app? Compare binary size, plugin support, security, and Live Updates to choose the right platform.", "image": "https://capawesome.io/assets/banners/cloud-build-and-deploy-capacitor-apps.png", "datePublished": "2026-07-18T00:00:00+00:00", "dateModified": "2026-07-18T00:00:00+00:00", "author": [ { "@type": "Person", "name": "Robin Genz", "url": "https://github.com/robingenz" } ], "publisher": { "@type": "Organization", "name": "Capawesome", "url": "https://capawesome.io", "logo": { "@type": "ImageObject", "url": "https://capawesome.io/assets/images/logo.svg" } }, "articleSection": "Capacitor", "keywords": ["Capacitor", "Electron", "Guides"], "isPartOf": { "@type": "Blog", "@id": "https://capawesome.io/blog/#blog" }, "mainEntityOfPage": "https://capawesome.io/blog/electron-vs-tauri-for-capacitor-apps/", "url": "https://capawesome.io/blog/electron-vs-tauri-for-capacitor-apps/" } { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://capawesome.io/" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://capawesome.io/blog/" }, { "@type": "ListItem", "position": 3, "name": "Electron vs. Tauri for Capacitor Apps", "item": "https://capawesome.io/blog/electron-vs-tauri-for-capacitor-apps/" } ] } {"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Electron vs. Tauri: which should you choose?", "acceptedAnswer": {"@type": "Answer", "text": "Choose Electron if you need broad plugin support, over-the-air Live Updates, or the simplest possible setup. Choose Tauri if binary size, memory footprint, and a hardened security model matter more than plugin breadth, and your app can work with web plus a curated set of plugins. Both platforms run the same Capacitor web build, so most application code stays identical between them. The table below summarizes the practical differences. Aspect Capacitor Electron Capacitor Tauri Binary size ~80–150 MB ~3–10 MB Webview Bundled Chromium System webview (WKWebView / WebView2 / WebKitGTK) Runtime / language Node.js Rust core Plugin support Any Electron or web implementation Built-in + curated + web only Web-bundle Live Updates Available Not available Dev toolchain npm only Rust toolchain required Version floor Capacitor 6+ / Electron 28+ Capacitor 8+ / Tauri 2+"}}, {"@type": "Question", "name": "When should you choose Electron?", "acceptedAnswer": {"@type": "Answer", "text": "Electron is the right call when: Your app depends on native plugins with Electron implementations, or on a wide range of plugins in general. You want to ship web-bundle Live Updates and push over-the-air patches to desktop users. You want the simplest setup with npm only and no extra toolchain. Predictable, consistent rendering across all three operating systems matters to you. Installer size and memory footprint are not primary constraints for your audience."}}, {"@type": "Question", "name": "When should you choose Tauri?", "acceptedAnswer": {"@type": "Answer", "text": "Tauri is the better fit when: You want a lean binary for a consumer, kiosk, or utility app where download size and memory matter. Security is a priority and you want a deny-by-default permission model with minimal grants. Your app works well with web implementations plus the curated set of supported plugins. You do not need over-the-air updates of your web layer and are comfortable shipping full signed binary updates. Your team can absorb the Rust toolchain requirement and the cross-engine webview testing that comes with system webviews."}}, {"@type": "Question", "name": "Is Tauri smaller than Electron?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, by a wide margin. A Capacitor Tauri build produces installers in the ~3–10 MB range because it reuses the system webview, while a Capacitor Electron build lands around ~80–150 MB because it bundles Chromium and Node.js."}}, {"@type": "Question", "name": "Can I use any Capacitor plugin with Tauri?", "acceptedAnswer": {"@type": "Answer", "text": "No. The Capacitor Tauri platform supports three tiers only: @capacitor/app built-in, a curated set of plugins on official tauri-plugin-* crates ( @capacitor/filesystem, @capacitor/preferences, @capacitor/dialog, @capacitor/local-notifications), and any plugin with a web implementation. Arbitrary native plugins do not run, because there is no Node.js runtime. The Capacitor Electron platform, by contrast, supports any plugin with an Electron or web implementation."}}, {"@type": "Question", "name": "Which one supports Live Updates?", "acceptedAnswer": {"@type": "Answer", "text": "Electron. The Capacitor Electron platform is the first Capacitor desktop platform with web-bundle Live Updates. Tauri compiles web assets into the binary and supports only full signed binary updates."}}, {"@type": "Question", "name": "Do both support macOS, Windows, and Linux?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Both platforms target macOS, Windows, and Linux, and both report isNativePlatform() as true."}}, {"@type": "Question", "name": "What does Capacitor.getPlatform() return on each?", "acceptedAnswer": {"@type": "Answer", "text": "It returns 'electron' on the Capacitor Electron platform and 'tauri' on the Capacitor Tauri platform, so you can branch on the desktop runtime at runtime."}}], "url": "https://capawesome.io/blog/electron-vs-tauri-for-capacitor-apps/"} ```