Site navigation

Varve on Chromebook

ChromeOS is not one platform: Varve can run in Chrome, as an installed web app, or as a Linux application inside ChromeOS's Linux development environment. This page chooses between them honestly, including what is not verified yet.

Choose a route

1. Browser tab no install

Open varve.studio/try/ in Chrome. The editor runs on the WASM engine with browser storage. This is the lowest-setup route to try on a current Chromebook, including managed devices where Linux is unavailable. It remains experimental: browser policy, storage, and device capabilities can limit the result, and this project has not yet run it on a physical Chromebook.

Best for: trying Varve, small documents, Chromebooks with Linux disabled.

2. Installed web app same build

From the same page, use Chrome's Install page as app action to get a standalone window and launcher icon. It shares storage with the tab, works offline after one online visit, and asks before applying an update. Installation can be blocked by an administrator on managed devices.

Best for: everyday browser use without a visible tab bar.

3. Linux application separate route

If the Linux development environment is enabled, install the ARM64 or x86_64 .deb to run the native Varve desktop application. This is not native ChromeOS Chrome and not an Android app. Google’s current support guidance lists hardware acceleration, including GPU and video decode, as unavailable for Linux apps; behavior is version/device dependent, so Varve does not promise acceleration in this route.

Best for: testing the native desktop feature set. GUI behavior on a Chromebook is unverified.

There is no native ChromeOS installer, and Android, Windows, or macOS packages are not substitutes. Do not install an x86_64 package on an ARM Chromebook (or vice versa).

Requirements

  • Browser route: a current Chromium-based browser (Chrome or Edge). Chromebooks ship Chrome, so this is always present. Firefox and Safari work with the download save fallback.
  • Linux route: Linux enabled in Settings → About ChromeOS → Developers, an ARM64 or x86_64 Chromebook (Chromebooks are ARM64; Intel/AMD models are x86_64), Debian 12+ inside the container, and roughly 2 GB of free space before installing. The package itself is about 49 MB and installs about 85 MB of files.
  • Memory: 8 GB Chromebooks are the reference target; 4 GB devices are expected to degrade through the adaptive profile rather than fail. Installed RAM is shared with ChromeOS, Android, and the Linux container — it is not what one tab receives.
  • No NPU or WebGPU guarantee: WebGPU is used only after a real adapter and device probe; Canvas2D is the authoritative fallback. The MediaTek NPU is not exposed to browsers or the Linux container and Varve does not use it.

What is tested, and when

AreaEvidenceStatus
Browser: install criteria, offline relaunch, update offer, storage cleanupProduction /try/ artifact, automated browser acceptance, 2026-09-12Verified in a desktop browser; ChromeOS device run pending
Browser: sample document, edit, save, reopen, export (SVG/JPEG/PNG)Production artifact, decoded pixel/geometry assertions, 2026-09-12Verified in a desktop browser; ChromeOS device run pending
Responsive layout, touch/pen input, virtual keyboard, back gesturePlaywright Chromium 151 on Linux emulation: 13 CSS viewports, touch/pen ownership, nested Back, and synthetic keyboard geometry, 2026-09-29Browser-regression-tested; ChromeOS, installed-PWA, and physical pen/keyboard behavior unverified
Linux ARM64 package metadata, checksums, glibc floor, dependency closurePublished v0.6.0 artifacts, byte verification and archive resolution, 2026-09-12Package verified; Crostini GUI unverified

Feature comparison

FeatureBrowser tabInstalled web appLinux app
Core editing (Design, Draw, Photo workspaces, layers, undo)Available (bounded demo)Same buildNative application
Motion and Email workspaces; Logo tools and shared Code panelNot includedNot includedImplemented (device run pending)
Print production (PDF/X, CMYK, ICC)Not includedNot includedImplemented; CUPS is commonly absent in the container
On-device AI modelsCapability-gated, optional; core editing never waits for a downloadSame buildImplemented; v0.6.0 AppImage lost its bundled runtime (fix on master), so prefer the .deb
FilesBrowser storage + File System Access where supported; download fallbackSame storage as the tabNative file dialogs in the Linux container
OfflineAfter one complete online visitAfter one complete online visitLocal application
UpdatesNew version offered on next visit; reload to applyIn-app update notice, applies after approvalManual: install the newer .deb (no apt repository)
Hardware accelerationCanvas2D authoritative; WebGPU only if a device probe succeedsSame as the tabNot provided by ChromeOS for Linux apps; expect software rendering

Managed (work or school) Chromebooks

Administrators control both routes. ChromeOS lets an administrator turn the Linux development environment off, and Chrome Enterprise policy can block, allow, or force-install web apps. If Linux is missing from Settings, or installation is unavailable, the option has been disabled by policy.

Contact your administrator. This project does not provide, and will not document, a way to bypass managed-device restrictions or ChromeOS security controls. The browser route may remain usable even when Linux or app installation is blocked; if policy blocks that too, there is no supported route on that device.

Set up and first project

  1. Browser route: follow the Browser Demo & Offline guide. It covers installing the web app, offline setup, saving versus recovery, storage cleanup, and moving work between browser and desktop.
  2. Linux route: follow the ChromeOS Linux guide from "Before you start". It includes the architecture check (uname -m), checksum verification, install, first launch, and uninstall with the data decision.
  3. Either route: open the sample document, make an edit, save it with an explicit destination, close and reopen it, and export once. If any step fails, the troubleshooting guide covers wrong architecture, missing libraries, blank windows, low space, blocked model downloads, and safe diagnostics.

Known limitations, stated plainly

  • The browser build is a bounded demo, not the full desktop product.
  • The public varve.studio demo is hosted on GitHub Pages, which cannot configure the cross-origin isolation headers required for shared-memory WASM; multi-threaded WASM is unavailable there. This describes the current public host, not all browser deployments, and does not establish a general speed comparison with desktop.
  • A browser can discard a tab under memory pressure. Recovery copies are a safety net, not a save: keep important work in a real file.
  • The Linux route has package-level evidence but no recorded GUI launch on a Chromebook. Rendering, input, fonts, suspend/resume, and printing remain unverified.
  • Uninstalling the installed app with "delete data", clearing browsing data, or removing the Linux environment all delete local work. Back up first.

Search Varve