Desktop 0.3.0 is available

Your JSTorrent update

The familiar JSTorrent, with a new Rust engine underneath.

Desktop 0.3.0 is now available from the JSTorrent website and through desktop updates. Android and extension store updates may arrive separately. Keep your downloaded files and follow the recovery steps below if access needs repair.

Your device and browser

Desktop

Desktop 0.3.0 is an ordinary JSTorrent update for Windows, macOS and Linux. Linux desktop support is best effort; AppImage and headless setup from source are described on the JSTorrent website. Desktop works on its own; the Chrome extension adds a browser view of the same library.

Android and ChromeOS

The Android replacement is rolling out gradually on Google Play. It requires Android 9 or newer and a supported 64-bit ARM or x86 device. If no update is available yet, keep using your installed app. Older 32-bit devices and Android 7 or 8 retain the old app; use a supported OS and device to move to the replacement. An unavailable store update is not a failed download to retry.

ChromeOS Linux

Choose the Linux setup explicitly when it is supported on your Chromebook. Android and Linux keep separate libraries. Switching backends does not automatically transfer torrents, files or folder access.

iOS is outside this release. Preview builds remain experimental and are separate from production updates.

Keep your library and folder access

Existing torrents and matching settings are imported best effort. Retained content is checked before it is treated as verified. A completed torrent may briefly show checking after the update.

If a download folder is unavailable, restore access or use the app’s repair action. Keep the downloaded files. Removing the app, clearing its storage or deleting a folder is not the normal repair procedure.

Quit the old desktop app before a manual replacement. If migration is blocked, follow the displayed recovery step and preserve the old library for a retry.

App and extension updates can arrive separately

If the connection page asks for an app or extension update, update that component through its usual store or update route. Fresh pairing may be needed after replacement. Open the native app and approve the new connection when prompted.

Android can still be used on its own while a companion update is unavailable. Repeated pairing attempts cannot install a missing store update.

Check features you depend on

The replacement does not promise every legacy feature. Old VPN-only, low-battery stop, search-plugin, locale or theme-override settings do not imply equivalent restrictions or behavior in the new app.

The replacement does not claim VPN confinement or SOCKS5 privacy guarantees. Review the release notes before updating if you rely on those features.

Privacy and support

Review usage-statistics preferences and the exact context before opening feedback. Website requests and embedded forms can receive information before you submit a response.

Support diagnostics are prepared locally for you to review and share voluntarily. Screenshots and public issue attachments can contain private information.