Close detail of umber swap chevrons with a sand core on mist paper.
Swap detail for the translator mark used across this install guide. Glyph Quill original glyph-swap geometry for factory-translator (not a Pot logo).

Update

  1. Open pot-app/pot-desktop Releases.
  2. Download the same class of asset you installed before.
  3. Run the new setup, open the new dmg, or replace the AppImage.
  4. Prove selection once after the bump.

Uninstall

Windows: use Apps & features for the Pot entry from the setup. macOS: remove the app you installed from the dmg. Linux: remove the deb package or delete the AppImage folder you created.

Avoid drift

Do not leave two translator doors half-updated. Document the surviving door on the ticket. More: /translator-releases · /translator-for-this-computer

Why this path matters

A local Pot client keeps translator work on a desk you control. GPL-3.0 builds give you named release assets you can document on a machine ticket. That is enough for travel laptops, student machines, and shared desks that need a selection overlay after install.

Keep Softonic-style mirrors out of the loop. Prefer GitHub Releases filenames for pot-app/pot-desktop. After every reimage, prove one selection translator pass before you call the machine ready.

Home: /. Releases: /translator-releases. Download safe: /translator-download-safe. First hour: /installed. Guides hub: /guides.

Glyph Quill publishes the install guide. Upstream remains at pot-app.com and pot-app/pot-desktop. When a tag drops an OS asset, re-check the live list before imaging a lab.

Family PCs and shared desks benefit from writing the update door beside the OS version. Windows setup, macOS dmg, Linux deb, and AppImage are different doors. Mixing them without notes creates duplicate installs and confused uninstalls.

When someone pastes a random download link into chat, ask for the GitHub Releases URL instead. The install path on this guide always returns to pot-app/pot-desktop.

Desk habits that survive reimages

Pin the Releases URL beside the hotkey list. Store API keys in the password tool you already trust. Keep .potext plugins in a folder named on the ticket. Review enabled services quarterly so unused cloud engines do not linger.

Clipboard listening is optional and intense. Use it for dedicated sprints, then turn it off. Screenshot OCR is for text you cannot highlight, not for every paragraph. Selection remains the everyday translator door.

If two people insist on different installers, pick one official path for demos and document exceptions. Boring tickets beat clever one-off downloads.

Teaching new users

Sit through three short documents using only the selection hotkey. Keep a browser tab as fallback for a week, then remove shady mirror bookmarks. Wrong-language replies are usually a service setting, not an installer failure.

Wayland users should read upstream shortcut notes before blaming the build. Windows users missing WebView2 should take the fix_webview2_runtime setup from the same tag instead of a random mirror.

Inventory note

Keep a one-line inventory entry after every change: date, filename, hotkey, service list, and plugin list. That line is enough for classroom rebuilds and contractor handoffs. If the line is missing, assume the translator desk is not ready even when the icon still launches.

Frequently asked questions

Is this translator guide free to follow?

Yes. Glyph Quill publishes install steps without a paywall so anyone can follow the translator path. Pot itself ships under GPL-3.0. Third-party API billing stays your responsibility and is separate from the program licence.

Where should I download the translator setup?

Prefer pot_*_x64-setup.exe, matching macOS dmg files, or Linux deb or AppImage from GitHub Releases for pot-app/pot-desktop. Keep Softonic-style mirrors out of the loop. Document the update door on the machine ticket so the next bump stays honest for shared desks.

Does the translator work offline after install?

The client can sit installed offline after download, but most cloud engines need network for each request. Offline-friendly paths need local engines such as Ollama or offline OCR plugins documented upstream.

How do I keep translator updates honest?

Return to the same GitHub Releases filename for the next bump. Avoid renamed translator wrappers from review portals. Write the filename beside the OS version on the machine ticket after every reimage.