Skip to main content

Install and first run

Requirements​

PlatformMinimum versionArchitecture
WindowsWindows 10 1809 or Windows 11x64, arm64
macOSmacOS 13 VenturaApple Silicon, Intel
LinuxUbuntu 22.04+ / Fedora 38+x64, arm64

Installers ship the runtime and the UI only; models download on first use. Reserve at least 2 GB of disk space, depending on the engines and quantization levels you pick.

Install​

Windows​

  1. Download the MSIX package from the release page.
  2. Install it, or run Add-AppxPackage .\Glyphix-1.0-x64.msix in PowerShell.
  3. The zip portable build runs Glyphix.Desktop.exe without installation.

macOS​

  1. Download the dmg and drag Glyphix into Applications.
  2. If macOS blocks the first launch, allow it under System Settings → Privacy & Security.
  3. Choose the arm64 build for Apple Silicon and x64 for Intel.

Linux​

# AppImage
chmod +x Glyphix-1.0-x86_64.AppImage
./Glyphix-1.0-x86_64.AppImage

# Debian / Ubuntu
sudo apt install ./glyphix_1.0.0_amd64.deb

On Wayland, system window decorations are preferred; if the tray is unavailable the app falls back to in-window status.

First run​

  1. Open the engine center and install a model pack at the default quantization. The app downloads, verifies SHA-256 and switches the active version atomically.
  2. Check the shared runtime — llama.cpp based engines share one runtime, installed once and referenced by several engines.
  3. Add files — drop PDF, PNG, JPEG or TIFF into the batch page; the queue de-duplicates automatically.
  4. Recognise — run with defaults, or adjust engine, language and concurrency in the batch bar.
  5. Verify and export — check the result views, then export to the format you need.

Data locations​

PlatformApp data
Windows%AppData%\Glyphix
macOS~/Library/Application Support/Glyphix
Linux$XDG_CONFIG_HOME/Glyphix (defaults to ~/.config/Glyphix)

Models, runtimes, logs and caches live there. Settings → Storage shows usage and can move the directory to another disk.

Uninstall​

  • Uninstalling the app keeps downloaded models. Remove the directory above to clean up completely.
  • To remove one engine's models, use the engine center rather than deleting folders, which leaves inconsistent install records.