--- title: "Pake: Turn Websites into Desktop Apps Without Electron" canonical: https://wavect.io/blog/pake-website-to-desktop-app/ language: en description: "Turn a website into a desktop app with Pake. Compare actual installer sizes, PWA alternatives, Google login limits, local builds and GitHub Actions workflows." image: "https://wavect.io/img/blog/headers/header_pake-website-to-desktop-app.png" --- [**Back**](/blog/overview/) [![Kevin Riedl](/img/team/kevin.webp)](/team/kevin-riedl/) [Kevin Riedl](/team/kevin-riedl/) https://linkedin.com/in/wsdt 12 min read · 22 Sep 2026 Last reviewed September 22, 2026 [**Next**](/blog/will-ai-kill-cross-platform-frameworks/) # Pake: Turn Websites into Desktop Apps Without Electron TL;DR Pake wraps websites and local web builds in a Tauri and Rust desktop shell using the platform WebView. It does not rewrite the interface or make a cloud service local. In release 3.17.0, the ChatGPT downloads range from a 3.54 MB Windows MSI to a 76 MB Linux AppImage, so under 10 MB is not universal and says nothing about RAM. Try browser installation for a simple personal window; consider Pake for a configurable package, then validate login, runtime dependencies, signing and the full user workflow. **Your most-used website may need its own window, not another bundled browser.** Pake packages a URL or local web build as a desktop app using Tauri and Rust. Its appeal is a small app shell, an application icon and desktop controls without maintaining an Electron project. The [Pake GitHub repository](https://github.com/tw93/Pake) showed approximately 61.6k stars when checked on 22 September 2026. This guide reviews [Pake 3.17.0, released on 20 September 2026](https://github.com/tw93/Pake/releases/tag/V3.17.0). It separates published package sizes from memory claims and explains the practical limits: system WebViews, Google sign-in, local routing and distributable builds. This is a source and release-artifact review, not a hands-on performance benchmark. ## What is Pake, and what does it actually convert? Pake is an open-source website-to-desktop-app packager. It puts an existing web interface inside a native desktop window, rather than translating HTML into native controls or rewriting your application. The website still supplies its content and business logic. Packaging an online AI service does not move its model onto your computer. The [project README](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/README.md) describes installers roughly 20 times smaller than Electron builds and apps typically below 10 MB. Treat that as the project's positioning, not a guarantee for every operating system, package format or website. A more accurate promise is: **Pake can avoid shipping a separate Electron browser runtime with each app.** ## Are Pake apps really under 10 MB? The release files tell a better story The downloadable files for the same ChatGPT wrapper vary considerably by format. These are GitHub's displayed **download sizes** from the [official Pake 3.17.0 release assets](https://github.com/tw93/Pake/releases/expanded_assets/V3.17.0), not installed footprints or RAM measurements. | Platform | Release asset | Download size | | --- | --- | --- | | macOS | `ChatGPT.dmg` | 9.42 MB | | Windows | `ChatGPT_x64.msi` | 3.54 MB | | Linux, Debian package | `ChatGPT_x86_64.deb` | 4.55 MB | | Linux, AppImage | `ChatGPT_x86_64.AppImage` | 76 MB | The same release also lists `DeepSeek.dmg` at 10.8 MB. Therefore, “every Pake app is under 10 MB” is demonstrably too broad. Package format matters. The release includes ChatGPT, Gemini and YouTube wrappers, but these are **Pake-distributed wrappers, not proof of an official client from the service provider**. Keep four measurements separate: download size, installed application size, additional runtime dependencies and runtime memory. A smaller installer proves only the first. We have not measured a matched Electron build, so this article does not present the 20x comparison as our own result. ## Pake vs Electron: the browser engine has moved, not disappeared [Electron's documentation](https://www.electronjs.org/docs/latest/) explains that Electron embeds Chromium and Node.js. This gives developers a controlled browser environment across desktop platforms. Pake's Tauri-based approach instead uses the operating system's WebView integration. The trade-off is less per-app runtime duplication, but more dependence on the target machine. [Tauri's WebView reference](https://v2.tauri.app/reference/webview-versions/) identifies different engines across operating systems: | Platform | WebView | What to check | | --- | --- | --- | | macOS | WKWebView / WebKit | Compatibility with the supported macOS versions. | | Windows | Microsoft Edge WebView2 | Runtime availability and its deployment policy. | | Linux | WebKitGTK | Distribution libraries, display environment and package format. | Windows WebView2 is Chromium-based. Calling Pake “Chromium-free” would therefore be misleading. The benefit is that your wrapper need not include its own full Electron runtime, not that browser rendering is free. Windows deployment also changes the size calculation. [Tauri's installer documentation](https://v2.tauri.app/distribute/windows-installer/) distinguishes downloading WebView2 when needed from bundling it for offline installation. A bundled runtime can add substantial size. Those are framework deployment options, not evidence that every Pake MSI includes the same runtime payload. ## How to turn a website into a desktop app with one command For the reviewed CLI version, this is the smallest useful example. Replace `https://example.com` with a website you are authorized to use. The command downloads and runs build tooling; review the package before running it. ``` npx pake-cli@3.17.0 https://example.com --name "MyWorkspace" ``` Alternatively, run `npm install -g pake-cli@3.17.0` to install the CLI globally, then use the `pake` command in the remaining examples. When no icon is specified, Pake attempts to fetch the site's favicon. A failed icon lookup may require a supplied icon file. **One command does not mean zero setup.** Pake recommends Node.js 22 or newer and requires Rust 1.85 or newer. Native compilation also needs platform tools: Xcode Command Line Tools on macOS, the appropriate C++ toolchain on Windows, and distribution-specific development libraries on Linux. Follow the [Tauri prerequisites](https://v2.tauri.app/start/prerequisites/) for the target platform before treating a missing compiler as a Pake defect. Build on suitable platform runners. Do not assume one invocation on a Mac produces signed macOS, Windows and Linux releases. The first build may need dependency downloads, and the generated package is normally written to the current working directory. On Windows, MSVC remains the default; version 3.17.0 also offers `--windows-toolchain gnu` for an existing MinGW/MSYS2 environment on x64. That is an alternative compiler setup, not a compiler-free build. ## Customize the window without rebuilding your web product After a global CLI installation, a practical starting point is: ``` pake https://example.com --name "MyWorkspace" --width 1280 --height 900 --activation-shortcut "CmdOrControl+Shift+9" --show-system-tray --enable-drag-drop ``` Use `--hide-title-bar` on macOS. On Windows and Linux, the corresponding window-decoration option is `--hide-window-decorations`; it also removes native window controls, so test whether the result remains usable. Shortcuts and drag-and-drop support deserve testing against the actual site's interactions. Pake also supports local CSS and JavaScript injection, covered in its [advanced customization guide](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/advanced-usage.md). A stylesheet can simplify an interface, but it cannot make an incompatible authentication flow supported. Review injected code like application code, especially when it runs inside a signed-in account. Avoid untrusted snippets and test selector-based changes after website updates. ## Pake vs a PWA: when is packaging worth it? For an individual who only wants a separate window and a launcher icon, try browser installation first. [MDN's web-app installation guide](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing) documents how installation varies by browser and platform. Installing a website and making it work offline are separate concerns. | Approach | A sensible starting point when | Main trade-off | | --- | --- | --- | | Browser-installed site / PWA | You primarily need an app-like window for personal use. | You stay within browser-provided installation and integration. | | Pake | You need a named desktop package and configurable shell around an existing web UI. | You inherit WebView compatibility and wrapper release maintenance. | | Custom Tauri application | Your product needs deliberately designed native integration. | You own application code, permissions and platform testing. | | Electron application | A controlled Chromium environment and Node.js integration justify the runtime. | You distribute and maintain that bundled runtime. | Our recommendation is to start with the least complex option that satisfies the required workflow. Pake is particularly interesting between browser installation and a custom desktop product. The broader decision about shared code and native development belongs in our [cross-platform framework strategy analysis](/blog/will-ai-kill-cross-platform-frameworks/), rather than being settled by an installer-size screenshot. ## Google login, Cloudflare loops and high memory: three common surprises The [Pake troubleshooting FAQ](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/faq.md) explicitly discusses rejected embedded sign-in, Cloudflare verification loops and substantial WebView memory use. These are important boundaries for “turn any website into an app.” A page opening successfully does not prove that the full user journey works. ### Google sign-in is not just a popup setting `--multi-window` can help popup-based flows, and `--safe-domain` controls which trusted hosts remain inside the wrapper. Neither overrides an identity provider's rules. [Google's OAuth policy](https://developers.google.com/identity/protocols/oauth2/policies) restricts authorization through embedded user-agents controlled by the developer. When a provider rejects the wrapper, use a supported browser flow or the provider's official client rather than disguising the WebView. ### A Cloudflare challenge loop may be a compatibility blocker Pake's FAQ reports that some protected sites, particularly on Linux WebKitGTK, may remain stuck in verification. It does not promise a reliable Pake-side fix. Treat this as a go/no-go test for the chosen site, not a reason to disable protections or promise a user-agent workaround. ### Small download, large WebView process The site's scripts, rendering and WebView processes still consume memory. An AI chat interface can remain resource-intensive in a small wrapper. Compare the full process group under the same workload, not just the small Rust launcher, and do not infer a fixed RAM saving from the download table. ## Can Pake package a local website or work offline? Yes, it accepts a local HTML file or a static build directory. For a directory, place `index.html` at the root: ``` pake ./dist --name "LocalDashboard" ``` There is a meaningful limitation: **local packaging supports hash routing, but not history-mode SPA routing** in the reviewed version. The [versioned Pake CLI reference](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/cli-usage.md) covers this restriction and the options used above. A locally packaged React or Vue frontend may therefore need a routing change before deep links work as expected. Bundling frontend files does not bundle your backend, cloud API or identity provider. To claim offline support, disconnect the network and test every essential workflow. A dashboard whose JavaScript loads locally but whose data still comes from a remote API is not an offline product. ## Pake JSON configuration for repeatable builds and AI agents For a team, put the intended window settings in a reviewed configuration file instead of reconstructing a long command. Save this as `app.json`; it follows the [Pake 3.17.0 configuration schema](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/schema/pake.schema.json): ``` { "$schema": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/schema/pake.schema.json", "url": "https://example.com", "name": "SupportDesk", "width": 1280, "height": 900, "activationShortcut": "CmdOrControl+Shift+9", "showSystemTray": true, "appVersion": "1.0.0" } ``` ``` pake --config app.json --json ``` The [documented automation contract](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/llms.txt) sends one JSON result to stdout and logs to stderr. Exit codes distinguish success (`0`), invalid input (`2`), build failure (`3`), missing environment or setup failure (`4`), and unexpected failure (`1`). **Do not accept `ok: true` as proof that every requested Linux format exists.** A multi-target build can succeed partially. Check `outputs[].format` and `warnings`, then verify the listed artifacts. Relative local paths resolve from the process working directory. Build success still does not test login, payments or file handling. ## Build Pake apps with GitHub Actions instead of a local toolchain The [Pake GitHub Actions guide](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/github-actions-usage.md) provides a hosted route: fork the repository, enable Actions, open **Build App With Pake CLI**, supply the URL and app settings, then run the workflow. Download the resulting artifacts from the completed workflow run. For a private business application, our recommendation is to review the workflow, pin the intended source version and minimize permissions. Keep credentials out of URLs, repository configuration and build logs. Store signing secrets through the platform's secret mechanism, not in the article's example JSON. A hosted runner removes local compiler setup; it does not remove supply-chain review or release testing. ## Signing, ownership and the Pake license exception Before distributing a wrapper to colleagues or customers, define who owns updates, regression tests and incident response. Follow the platform's release requirements. For example, [Tauri's macOS signing guide](https://v2.tauri.app/distribute/sign/macos/) explains signing and notarization for distribution. Do not make disabling operating-system protections the onboarding process. Pake is GPL-3.0-or-later, with a specific [output exception](https://raw.githubusercontent.com/tw93/Pake/V3.17.0/LICENSE-EXCEPTION). Standard packaging does not by itself require the generated app to be released under the GPL; modified Pake source remains subject to the relevant GPL obligations. This distinction is not permission to redistribute another service's trademarks, content or functionality against its terms. Review the exception and your intended distribution separately. ## A practical acceptance checklist before shipping your wrapper These are our proposed acceptance checks, not tests we have performed on the published binaries: | Area | Required evidence | | --- | --- | | Identity and navigation | Sign-in, MFA, logout, account switching, external links and reopening the app all work. | | Core workflows | Uploads, downloads, drag-and-drop, keyboard access, and any required camera or microphone flows pass. | | Resource use | Record download size, installed size, runtime dependencies and full process-group memory separately. | | Distribution and recovery | A clean target machine can install, update and remove the app; a failed rollout has a rollback path. | For a customer-facing desktop experience, our [custom software development service](/services/software-development/) can help assess the boundary between a wrapper and a product. The [Offlinery case study](/case-studies/offlinery/) provides separate product-delivery context, not a Pake deployment claim. Use the [software QA checklist before launch](/software-development-guide/software-qa-checklist-before-launch/) to structure validation, or [discuss your website-to-desktop requirements with Wavect](/contact/). *Documentation and release metadata checked on 22 September 2026. Commands are documentation-based examples; runtime performance and provider compatibility must be verified for your deployment.* ## Frequently asked questions about Pake ### What is Pake? Pake is an open-source CLI that packages a website or local static web build inside a Tauri and Rust desktop shell. It uses the platform WebView rather than embedding an Electron runtime, but the interface remains a web application. ### Are all Pake apps smaller than 10 MB? No. Pake 3.17.0 lists its ChatGPT wrapper at 3.54 MB as a Windows MSI and 76 MB as a Linux AppImage. These are download sizes, not installed size or memory measurements. ### Does Pake always use less RAM than Electron? No fixed saving is established here. The page and its WebView still use memory. Measure the complete process group under an equivalent workload; installer size is not a memory benchmark. ### Why does Google login fail inside a Pake app? Identity providers can reject embedded WebViews. Popup and navigation options do not override provider policy. Use a supported browser authorization flow or the service provider's official client when the wrapper is rejected. ### Can Pake package a local React or Vue app for offline use? It can package a static directory containing index.html. The reviewed version supports hash routing, not history-mode SPA routing. Offline use also requires that essential assets, data and workflows do not depend on unavailable remote services. ### When should I choose a PWA instead of Pake? Start with browser installation when you only need an independent window and launcher icon. Consider Pake when a separately packaged desktop shell and its configuration provide a clear benefit. ### Are Pake's ChatGPT and Gemini downloads official vendor apps? They are wrappers distributed by the Pake project. Their presence in Pake releases does not establish that OpenAI, Google or another service provider publishes or endorses those clients. ### Can a Pake-generated app be distributed under a proprietary license? Pake has an output exception stating that standard packaging does not by itself impose the GPL on generated applications. Modified Pake source and third-party service terms require separate review. ### What should an automated Pake build check besides ok: true? Check the process exit code, warnings and outputs[].format, and verify the generated artifacts. Linux multi-target builds can report success while producing fewer formats than requested. Functional acceptance tests are still separate. ## Final thoughts Pake makes a useful middle ground accessible: a configurable desktop shell for a web product that already exists. Its advantage is avoiding unnecessary runtime duplication, not magically removing browser costs. Use the actual package format, authentication compatibility and acceptance criteria to decide whether it is better than browser installation or a custom desktop application. ## You may also like.. [**Will AI Kill Cross-Platform Frameworks?** Explore the broader architecture decision about shared code, native clients and the cost of verification.](/blog/will-ai-kill-cross-platform-frameworks/) Architecture and platforms ## Continue through this cluster Framework, platform and system-design choices that affect delivery over the long term. [Start with the cornerstone**Smart City Architecture Best Practices: MQTT, LoRaWAN, Kubernetes and Terraform**](/blog/smart-city-architecture-best-practices-2026/) - [Flughafen Innsbruck: An Independent Software, Digitalisation and AI Opportunity Map](/blog/flughafen-innsbruck-software-ai-opportunity-map/) - [EU Battery Passport Software Architecture for 2027](/blog/eu-battery-passport-software-architecture-2027/) - [EU Data Act: Connected-Product API Checklist](/blog/eu-data-act-connected-product-api-2026/) - [Cursor Origin vs GitHub: Should Your Team Switch?](/blog/cursor-origin-vs-github-code-hosting/) - [MoneyPrinterTurbo Review 2026: Free AI Video, Real Costs](/blog/moneyprinterturbo-review-2026/) [**Back**](/blog/overview/) [![Kevin Riedl](/img/team/kevin.webp)](/team/kevin-riedl/) [Kevin Riedl](/team/kevin-riedl/) https://linkedin.com/in/wsdt 12 min read · 22 Sep 2026 Last reviewed September 22, 2026 [**Next**](/blog/will-ai-kill-cross-platform-frameworks/) ## Structured Data ```json { "@context": "https://schema.org", "@graph": [ { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ], "employee": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "founder": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "legalRepresentative": [ { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } } ], "name": "Wavect GmbH", "subjectOf": { "@id": "https://wavect.io/verified-claims.json#dataset", "@type": "Dataset", "creator": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "description": "A machine-readable registry of quantitative and qualitative claims published by Wavect, with review dates, localized page appearances and public third-party citations where available.", "inLanguage": "en", "isAccessibleForFree": true, "license": "https://creativecommons.org/licenses/by/4.0/", "name": "Wavect verified publication claims", "url": "https://wavect.io/verified-claims.json" }, "url": "https://wavect.io/" }, { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Kevin Riedl", "sameAs": [ "https://www.wikidata.org/wiki/Q139796365", "https://www.linkedin.com/in/wsdt", "https://github.com/wsdt" ], "url": "https://wavect.io/team/kevin-riedl/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/team/christof-jori/#person", "@type": "Person", "jobTitle": "Managing Director", "name": "Christof Jori", "sameAs": [ "https://www.wikidata.org/wiki/Q139796367", "https://www.linkedin.com/in/jocr77/", "https://github.com/jo-chris" ], "url": "https://wavect.io/team/christof-jori/", "worksFor": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] } }, { "@id": "https://wavect.io/#website", "@type": "WebSite", "inLanguage": [ "en", "de", "es", "zh" ], "name": "Wavect", "potentialAction": { "@type": "SearchAction", "query-input": "required name=search_term_string", "target": { "@type": "EntryPoint", "urlTemplate": "https://wavect.io/search/?q={search_term_string}" } }, "publisher": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "url": "https://wavect.io/" }, { "@id": "https://wavect.io/blog/pake-website-to-desktop-app/#webpage", "@type": "WebPage", "dateModified": "2026-09-22", "inLanguage": "en", "isPartOf": { "@id": "https://wavect.io/#website", "@type": "WebSite" }, "lastReviewed": "2026-09-22", "url": "https://wavect.io/blog/pake-website-to-desktop-app/" } ] } ``` ```json { "@context": "https://schema.org", "@type": "BlogPosting", "abstract": "Pake wraps websites and local web builds in a Tauri and Rust desktop shell using the platform WebView. It does not rewrite the interface or make a cloud service local. In release 3.17.0, the ChatGPT downloads range from a 3.54 MB Windows MSI to a 76 MB Linux AppImage, so under 10 MB is not universal and says nothing about RAM. Try browser installation for a simple personal window; consider Pake for a configurable package, then validate login, runtime dependencies, signing and the full user workflow.", "articleBody": " Blog overview/Delivery and QA/Architecture and platforms Pake: Turn Websites into Desktop Apps Without Electron TL;DR Pake wraps websites and local web builds in a Tauri and Rust desktop shell using the platform WebView. It does not rewrite the interface or make a cloud service local. In release 3.17.0, the ChatGPT downloads range from a 3.54 MB Windows MSI to a 76 MB Linux AppImage, so under 10 MB is not universal and says nothing about RAM. Try browser installation for a simple personal window; consider Pake for a configurable package, then validate login, runtime dependencies, signing and the full user workflow. Your most-used website may need its own window, not another bundled browser. Pake packages a URL or local web build as a desktop app using Tauri and Rust. Its appeal is a small app shell, an application icon and desktop controls without maintaining an Electron project. The Pake GitHub repository showed approximately 61.6k stars when checked on 22 September 2026. This guide reviews Pake 3.17.0, released on 20 September 2026. It separates published package sizes from memory claims and explains the practical limits: system WebViews, Google sign-in, local routing and distributable builds. This is a source and release-artifact review, not a hands-on performance benchmark. What is Pake, and what does it actually convert? Pake is an open-source website-to-desktop-app packager. It puts an existing web interface inside a native desktop window, rather than translating HTML into native controls or rewriting your application. The website still supplies its content and business logic. Packaging an online AI service does not move its model onto your computer. The project README describes installers roughly 20 times smaller than Electron builds and apps typically below 10 MB. Treat that as the project's positioning, not a guarantee for every operating system, package format or website. A more accurate promise is: Pake can avoid shipping a separate Electron browser runtime with each app. Are Pake apps really under 10 MB? The release files tell a better story The downloadable files for the same ChatGPT wrapper vary considerably by format. These are GitHub's displayed download sizes from the official Pake 3.17.0 release assets, not installed footprints or RAM measurements. Published Pake 3.17.0 ChatGPT wrapper downloads, checked 22 September 2026 PlatformRelease assetDownload size macOSChatGPT.dmg9.42 MB WindowsChatGPT_x64.msi3.54 MB Linux, Debian packageChatGPT_x86_64.deb4.55 MB Linux, AppImageChatGPT_x86_64.AppImage76 MB The same release also lists DeepSeek.dmg at 10.8 MB. Therefore, “every Pake app is under 10 MB” is demonstrably too broad. Package format matters. The release includes ChatGPT, Gemini and YouTube wrappers, but these are Pake-distributed wrappers, not proof of an official client from the service provider. Keep four measurements separate: download size, installed application size, additional runtime dependencies and runtime memory. A smaller installer proves only the first. We have not measured a matched Electron build, so this article does not present the 20x comparison as our own result. Pake vs Electron: the browser engine has moved, not disappeared Electron's documentation explains that Electron embeds Chromium and Node.js. This gives developers a controlled browser environment across desktop platforms. Pake's Tauri-based approach instead uses the operating system's WebView integration. The trade-off is less per-app runtime duplication, but more dependence on the target machine. Tauri's WebView reference identifies different engines across operating systems: The desktop WebView environment that a Pake app depends on PlatformWebViewWhat to check macOSWKWebView / WebKitCompatibility with the supported macOS versions. WindowsMicrosoft Edge WebView2Runtime availability and its deployment policy. LinuxWebKitGTKDistribution libraries, display environment and package format. Windows WebView2 is Chromium-based. Calling Pake “Chromium-free” would therefore be misleading. The benefit is that your wrapper need not include its own full Electron runtime, not that browser rendering is free. Windows deployment also changes the size calculation. Tauri's installer documentation distinguishes downloading WebView2 when needed from bundling it for offline installation. A bundled runtime can add substantial size. Those are framework deployment options, not evidence that every Pake MSI includes the same runtime payload. How to turn a website into a desktop app with one command For the reviewed CLI version, this is the smallest useful example. Replace https://example.com with a website you are authorized to use. The command downloads and runs build tooling; review the package before running it. npx pake-cli@3.17.0 https://example.com --name \"MyWorkspace\" Alternatively, run npm install -g pake-cli@3.17.0 to install the CLI globally, then use the pake command in the remaining examples. When no icon is specified, Pake", "articleSection": "Desktop Engineering", "author": { "@id": "https://wavect.io/team/kevin-riedl/#person", "@type": "Person", "name": "Kevin Riedl", "sameAs": [ "https://www.wikidata.org/wiki/Q139796365", "https://www.linkedin.com/in/wsdt", "https://github.com/wsdt" ], "url": "https://wavect.io/team/kevin-riedl/" }, "citation": [ { "@type": "WebPage", "name": "Pake GitHub repository", "url": "https://github.com/tw93/Pake" }, { "@type": "WebPage", "name": "Pake 3.17.0, released on 20 September 2026", "url": "https://github.com/tw93/Pake/releases/tag/V3.17.0" }, { "@type": "WebPage", "name": "project README", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/README.md" }, { "@type": "WebPage", "name": "official Pake 3.17.0 release assets", "url": "https://github.com/tw93/Pake/releases/expanded_assets/V3.17.0" }, { "@type": "WebPage", "name": "Electron's documentation", "url": "https://www.electronjs.org/docs/latest/" }, { "@type": "WebPage", "name": "Tauri's WebView reference", "url": "https://v2.tauri.app/reference/webview-versions/" }, { "@type": "WebPage", "name": "Tauri's installer documentation", "url": "https://v2.tauri.app/distribute/windows-installer/" }, { "@type": "WebPage", "name": "Tauri prerequisites", "url": "https://v2.tauri.app/start/prerequisites/" }, { "@type": "WebPage", "name": "advanced customization guide", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/advanced-usage.md" }, { "@type": "WebPage", "name": "MDN's web-app installation guide", "url": "https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing" }, { "@type": "WebPage", "name": "Pake troubleshooting FAQ", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/faq.md" }, { "@type": "WebPage", "name": "Google's OAuth policy", "url": "https://developers.google.com/identity/protocols/oauth2/policies" }, { "@type": "WebPage", "name": "versioned Pake CLI reference", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/cli-usage.md" }, { "@type": "WebPage", "name": "Pake 3.17.0 configuration schema", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/schema/pake.schema.json" }, { "@type": "WebPage", "name": "documented automation contract", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/llms.txt" }, { "@type": "WebPage", "name": "Pake GitHub Actions guide", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/docs/github-actions-usage.md" }, { "@type": "WebPage", "name": "Tauri's macOS signing guide", "url": "https://v2.tauri.app/distribute/sign/macos/" }, { "@type": "WebPage", "name": "output exception", "url": "https://raw.githubusercontent.com/tw93/Pake/V3.17.0/LICENSE-EXCEPTION" } ], "dateModified": "2026-09-22", "datePublished": "2026-09-22", "description": "Pake wraps websites and local web builds in a Tauri and Rust desktop shell using the platform WebView. It does not rewrite the interface or make a cloud service local. In release 3.17.0, the ChatGPT downloads range from a 3.54 MB Windows MSI to a 76 MB Linux AppImage, so under 10 MB is not universal and says nothing about RAM. Try browser installation for a simple personal window; consider Pake for a configurable package, then validate login, runtime dependencies, signing and the full user workflow.", "headline": "Pake: Turn Websites into Desktop Apps Without Electron", "image": "https://wavect.io/img/blog/headers/header_pake-website-to-desktop-app.svg", "inLanguage": "en", "keywords": "Pake, Desktop apps, WebView", "mainEntityOfPage": { "@id": "https://wavect.io/blog/pake-website-to-desktop-app/", "@type": "WebPage" }, "publisher": { "@id": "https://wavect.io/#organization", "@type": [ "Organization", "ProfessionalService", "LocalBusiness" ] }, "url": "https://wavect.io/blog/pake-website-to-desktop-app/", "wordCount": 2724 } ``` ```json { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "item": "https://wavect.io/", "name": "Home", "position": 1 }, { "@type": "ListItem", "item": "https://wavect.io/blog/overview/", "name": "Blog overview", "position": 2 }, { "@type": "ListItem", "item": "https://wavect.io/blog/topics/delivery-qa/", "name": "Delivery and QA", "position": 3 }, { "@type": "ListItem", "item": "https://wavect.io/blog/clusters/architecture-platforms/", "name": "Architecture and platforms", "position": 4 }, { "@type": "ListItem", "item": "https://wavect.io/blog/pake-website-to-desktop-app/", "name": "Pake: Turn Websites into Desktop Apps Without Electron", "position": 5 } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Pake is an open-source CLI that packages a website or local static web build inside a Tauri and Rust desktop shell. It uses the platform WebView rather than embedding an Electron runtime, but the interface remains a web application." }, "name": "What is Pake?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "No. Pake 3.17.0 lists its ChatGPT wrapper at 3.54 MB as a Windows MSI and 76 MB as a Linux AppImage. These are download sizes, not installed size or memory measurements." }, "name": "Are all Pake apps smaller than 10 MB?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "No fixed saving is established here. The page and its WebView still use memory. Measure the complete process group under an equivalent workload; installer size is not a memory benchmark." }, "name": "Does Pake always use less RAM than Electron?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Identity providers can reject embedded WebViews. Popup and navigation options do not override provider policy. Use a supported browser authorization flow or the service provider's official client when the wrapper is rejected." }, "name": "Why does Google login fail inside a Pake app?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "It can package a static directory containing index.html. The reviewed version supports hash routing, not history-mode SPA routing. Offline use also requires that essential assets, data and workflows do not depend on unavailable remote services." }, "name": "Can Pake package a local React or Vue app for offline use?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Start with browser installation when you only need an independent window and launcher icon. Consider Pake when a separately packaged desktop shell and its configuration provide a clear benefit." }, "name": "When should I choose a PWA instead of Pake?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "They are wrappers distributed by the Pake project. Their presence in Pake releases does not establish that OpenAI, Google or another service provider publishes or endorses those clients." }, "name": "Are Pake's ChatGPT and Gemini downloads official vendor apps?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Pake has an output exception stating that standard packaging does not by itself impose the GPL on generated applications. Modified Pake source and third-party service terms require separate review." }, "name": "Can a Pake-generated app be distributed under a proprietary license?" }, { "@type": "Question", "acceptedAnswer": { "@type": "Answer", "text": "Check the process exit code, warnings and outputs[].format, and verify the generated artifacts. Linux multi-target builds can report success while producing fewer formats than requested. Functional acceptance tests are still separate." }, "name": "What should an automated Pake build check besides ok: true?" } ] } ```