Licasa is an image viewer and editor for the Linux desktop inspired by Google's Picasa Photo Viewer. It opens photos from your file manager in a fullscreen viewer or floating windows.
Licasa is an independent open-source project and is not affiliated with or endorsed by Google.
Caution
Upgrading from 0.8.1? Fully quit Licasa before installing.
Save your edits, finish exports and close dialogs. Focus the Licasa viewer and press Ctrl+Shift+Q. Do this for each running copy, including copies in other user sessions if applicable.
Arch users: do this before starting pacman. Follow the upgrade checklist below.
Download Licasa
Download published releases · 0.9.5 release notes · 0.9.6 release notes
- View photos fullscreen or in a floating window, then crop, adjust, and export them.
- Open JPEG, PNG, TIFF, WebP, HEIC/HEIF, JPEG XL, AVIF, JPEG 2000, and RAW previews.
- Play Motion Photos and animated APNG files.
- Type exact adjustment values and keep independent edits in each window.
- Confirm before overwriting an original, or choose Save as a copy.
- Export to 14 formats with tailored settings, linked dimensions and estimated file size.
If you try it, report a bug or suggest a feature.
In action
Open a photo — From the desktop into the fullscreen viewer.
Resize a floating window — Open a photo, move it, and resize it on the desktop.
Keep multiple windows open — Open additional views and arrange floating windows.
Install
Choose the package built for your distribution. All current packages target
x86-64 Intel/AMD Linux. The Ubuntu native package requires Ubuntu 24.04;
the Debian native package requires Debian 13 (Trixie). Their Qt, JPEG and FFmpeg
libraries differ, so editing dependency names cannot make one package work on
the other distribution.
Before updating an existing installation
- Fully quit the old version as described in the warning above.
- Use the same package format and the matching distribution package,
following the checksum and installation commands below.
- Launch 0.9.5 once after installing, then check Settings → Background
process matches your preference. Recognized, unmodified startup entries
migrate automatically; a settings reset or reboot is not normally needed.
If switching package formats, disable Background process in the old copy
and fully quit it before enabling background mode in the new copy. Startup
preferences belong to each installation.
Future updates: Store-installed Snaps follow their tracked channel
automatically unless updates are held. GitHub downloads need manual installation
for each release unless you separately configure a package repository. Licasa's
background setting does not download updates.
From 0.9.0, managed AppImage and native package installers can stop a verified
idle background viewer. If an update is refused because Licasa is busy or its
running copy cannot be verified, finish your work, fully quit and retry.
Snap (systems with Snapd)
Install the version currently published to the stable Store channel:
sudo snap install licasa
For an existing Store installation, check its tracked channel for updates:
sudo snap refresh licasa
snap list licasa
A release .snap file is installed or updated manually with the same command:
sha256sum -c licasa_0.9.5_amd64.snap.sha256 &&
sudo snap install --dangerous ./licasa_0.9.5_amd64.snap
--dangerous bypasses Store assertion verification for a local file. Keep
checking the published checksum and obtain the file from the trusted release.
Local-file installations do not automatically follow Store updates.
To switch a local-file installation to the stable Store channel for automatic
updates, fully quit Licasa, then run:
sudo snap refresh --amend licasa --channel=stable
Ubuntu 24.04 (amd64)
Download the Ubuntu .deb and its checksum file, then run these commands in
the download directory. APT resolves the runtime and lifecycle dependencies.
On Ubuntu 26.04, use the AppImage instructions below.
sha256sum -c licasa_0.9.5-1_amd64.deb.sha256 &&
sudo apt install ./licasa_0.9.5-1_amd64.deb
Debian 13 / Trixie (amd64, experimental)
The native Debian package is available for testing and remains in development
in the support matrix. Use the Debian-specific +deb13 package, built against
Debian's Qt 6.8.2 and multimedia libraries:
sha256sum -c licasa_0.9.5-1+deb13_amd64.deb.sha256 &&
sudo apt install ./licasa_0.9.5-1+deb13_amd64.deb
Fedora 44 (x86-64)
sha256sum -c licasa-appimage-0.9.5-1.fc44.x86_64.rpm.sha256 &&
sudo dnf install ./licasa-appimage-0.9.5-1.fc44.x86_64.rpm
The RPM installs the bundled runtime through DNF and includes native transaction
coordination. It is a different installation from a per-user AppImage.
Arch Linux (x86-64)
The ready-to-install package includes the lifecycle helper and pre-transaction
hook:
sha256sum -c licasa-appimage-0.9.5-1-x86_64.pkg.tar.zst.sha256 &&
sudo pacman -U ./licasa-appimage-0.9.5-1-x86_64.pkg.tar.zst
To build the Arch package yourself, download PKGBUILD, PKGBUILD.sha256,
PKGBUILD.sources.sha256, native_lifecycle.py, licasa.install, and
licasa-lifecycle.hook from the same release into one directory. Review
the recipe and scripts before building. The helper, install script and hook are
required inputs; copying only PKGBUILD is insufficient.
sha256sum -c PKGBUILD.sha256 &&
sha256sum -c PKGBUILD.sources.sha256 &&
makepkg -si
Run makepkg as your regular user. It verifies/downloads the matching AppImage
and asks the package manager to install the result. Later transactions use the
installed hook to refuse unsafe replacement. Before the first upgrade or removal
of a 0.8.1 package, fully quit Licasa; the incoming hook cannot protect that first
transaction.
Managed AppImage (compatible x86-64 glibc desktops)
Download the AppImage, installer and both checksum files from the same release.
Run the installer as your regular desktop user, without sudo:
sha256sum -c Licasa-0.9.5-x86_64.AppImage.sha256 &&
sha256sum -c install-licasa-appimage.sh.sha256 &&
bash install-licasa-appimage.sh ./Licasa-0.9.5-x86_64.AppImage
This installs Licasa (AppImage) under ~/.local/opt/licasa-appimage, with a
desktop entry and icon. It extracts the runtime, so FUSE is unnecessary for the
installed copy. Managed installation and its launcher require Python 3,
flock and the standard tools checked by the installer. Keep Python 3 and
flock installed afterward. The portable runtime uses a glibc 2.39 baseline and
still needs compatible system desktop libraries.
Raw portable AppImage
To run the downloaded file directly, without the managed installer:
sha256sum -c Licasa-0.9.5-x86_64.AppImage.sha256 &&
chmod +x Licasa-0.9.5-x86_64.AppImage &&
./Licasa-0.9.5-x86_64.AppImage
Fully quit before every replacement. Keep the file location/name used by
your shortcuts. If changing it, disable background mode in the old copy before
quitting, then enable it in the new copy if wanted. The same glibc and desktop
library requirements apply. If direct execution fails with a FUSE error, use
the FUSE-free managed installation above.
Uninstall
Finish work and fully quit first, especially when removing an older build.
Use the manager for the package actually installed:
# Run only the command for your installed package:
sudo apt remove licasa # Ubuntu or Debian native package
sudo dnf remove licasa-appimage # Fedora RPM
sudo pacman -R licasa-appimage # Arch package
sudo snap remove licasa # Snap
For managed AppImage, use its saved removal script as your regular user:
bash "$HOME/.local/opt/licasa-appimage/install-licasa-appimage.sh" --uninstall
The managed remover handles its viewer, desktop entry, icon and unmodified
startup integration. A raw portable file can be deleted after quitting;
remove any desktop entry you created manually. Local deployment can share
~/.local with unrelated software: do not remove that entire prefix to uninstall
Licasa.
Troubleshooting and logs
For an AppImage support report without starting the viewer:
bash install-licasa-appimage.sh --diagnose ./Licasa-0.9.5-x86_64.AppImage > licasa-support.txt
Omit the AppImage filename to inspect an existing installation. The report checks
system tools and the installation destination, plus libraries of an installed
copy when present. It does not extract or validate the libraries inside an
uninstalled AppImage. Review the report before sharing it.
The AppImage installer keeps a private log at
$XDG_STATE_HOME/licasa/installation.log (normally
~/.local/state/licasa/installation.log), with one rotated copy. The viewer's
warning/error log is $XDG_STATE_HOME/licasa/errors.log (normally
~/.local/state/licasa/errors.log); Snap uses its own user data when
XDG_STATE_HOME has no absolute path. Logs stay local and may contain photo or
installation paths. Review them before attaching them to an
issue.
Include the Licasa version, package filename, distribution, desktop and session
type, plus the exact command/error and support report when applicable.
Package support and runtime details
| Package / target |
Architecture / libc baseline |
Qt runtime |
Candidate qualification |
| ubuntu-deb / Ubuntu 24.04 |
x86-64 / glibc ≥ 2.39 |
6.4.2 |
Required before stable |
| debian-deb / Debian 13 (Trixie) |
x86-64 / glibc ≥ 2.41 |
6.8.2 |
In development; not a published support claim |
| debian-deb / Debian 13 / MATE X11 / native GTK file picker |
x86-64 / glibc ≥ 2.41 |
6.8.2 |
In development; not a published support claim |
| appimage / Ubuntu 22.04 |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| appimage / Ubuntu 24.04 |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| appimage / Ubuntu 26.04 |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| appimage / Debian 13 (Trixie) |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| appimage / Debian 13 / MATE X11 / AT-SPI keyboard accessibility |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| appimage / Fedora 44 |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| appimage / Arch Linux (rolling; tested image recorded in evidence) |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| rpm / Fedora 44 |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| arch / Arch Linux (rolling; tested image recorded in evidence) |
x86-64 / glibc ≥ 2.35 |
6.4.2 |
Required before stable |
| snap / Ubuntu 24.04 / GNOME X11 and Wayland |
x86-64 / glibc ≥ 2.39 |
6.4.2 |
Required before stable |
| snap / Ubuntu 24.04 / Plasma X11 and Wayland |
x86-64 / glibc ≥ 2.39 |
6.4.2 |
Required before stable |
Build the Ubuntu package and AppImage
From the repository root, with Docker installed:
docker build -f packaging/build-deb.Dockerfile -t licasa-deb-builder packaging
mkdir -p build/deb-output
docker run --rm -v "$PWD:/source:ro" -v "$PWD/build/deb-output:/output" \
licasa-deb-builder bash /source/packaging/verify-fresh-build.sh
Build the AppImage and its portable runtime in the Ubuntu 22.04 builder.
docker build -f packaging/build-appimage.Dockerfile -t licasa-appimage-builder packaging
mkdir -p build/appimage-work build/appimage-output
docker run --rm --user "$(id -u):$(id -g)" -e HOME=/work -e PYTHONDONTWRITEBYTECODE=1 \
-v "$PWD:/source:ro" -v "$PWD/build/appimage-work:/work" \
-v "$PWD/build/appimage-output:/output" licasa-appimage-builder \
python3 /source/tools/build_appimage.py --work-dir /work --output-dir /output --tools-dir /work/tools
install -m 0755 packaging/install-licasa-appimage.sh build/appimage-output/
(cd build/appimage-output && sha256sum install-licasa-appimage.sh > install-licasa-appimage.sh.sha256)
Verify the local package checksums.
(cd build/deb-output && sha256sum -c ./*.sha256)
(cd build/appimage-output && sha256sum -c ./*.sha256)
Install a Local development copy
For an already configured and built CMake tree, run as your regular user:
python3 tools/deploy_local.py --build-dir ./build --launch
This installs Licasa (Local) into ~/.local and launches it. It is separate
from the downloaded packages.
Translations
Licasa uses Qt Linguist catalogs in translations/. To update
the source strings or compile the catalogs, configure the project with Qt's
LinguistTools package installed, then run:
cmake --build ./build --target update_translations
cmake --build ./build --target release_translations
Edit the .ts catalog after updating it. In Settings, Language offers
System default, English, and Svenska. The choice is saved and applies
immediately to open windows. System default follows the computer's UI language,
with English as the fallback. Native file-dialog controls follow the desktop's
language; reopen an existing dialog to use updated application labels and filters.
The Swedish catalog (licasa_sv.ts) builds on
yeager's contribution in PR #7.
License
Licasa's first-party source is licensed under the BSD 2-Clause License. Third-party components and test fixtures have their own licenses, which are retained with the distributed materials.