LichiiField Guide
Project GitHub
Getting started

Find the Lichii Emulator download

This independent guide links to downloads hosted by the Lichii developers on GitHub. Open the release, check the repository name, then choose an application package that matches your computer.

Open GitHub Releases
Anatomy of a release file
lichii-windows-x86_64.zip

Find the release and its assets

  1. Look for zortos293/Lichii at the top of the GitHub page. A fork can have a similar name and a different owner. The project README links back to the releases it distributes.
  2. Open the release title. Keep the tag, such as build-130, with your download so you can find the same instructions again. Expand Assets below the release notes.
  3. Look for a filename beginning with lichii- and containing your operating system. The two GitHub entries labeled Source code contain the project files for developers. Unpacking one will leave you looking at a source tree.

Project download instructions

Read a release filename

Here is how to read the assets attached to build 130. Open the tag you intend to install and compare its own list before choosing a file.

Windows · x86_64
lichii-windows-x86_64.zip contains the standard application. The separate -pgo.zip is a profile-guided build for the same architecture.
Mac · arm64
lichii-macos-arm64.dmg is a disk image for Apple silicon. The ZIP beside it packages the application for the same chip. Neither is an Intel Mac build.
Linux · x86_64 or aarch64
Choose your architecture first, then pick an AppImage or a tar.gz. The release notes list the AppImage’s glibc requirement and the archive’s reliance on installed libraries.

Build 130 asset listBuild 130 packaging notes

Compare the downloaded file with GitHub

GitHub lists a SHA-256 digest beside each application asset in this release. Hash the unopened file on your computer, then compare all 64 hexadecimal characters with the entry for that exact filename. Letter case makes no difference.

Windows PowerShell
In the folder containing the standard Windows ZIP, run the command below. Read the Hash column. The PGO ZIP has a different digest.
macOS or Linux
Use shasum -a 256 on macOS or sha256sum on Linux, followed by the filename in quotes. Use the digest for the DMG, ZIP or AppImage you actually saved.
Get-FileHash -Algorithm SHA256 .\lichii-windows-x86_64.zip

A mismatch is a reason to discard that copy and download again from the release page. A match identifies the bytes GitHub lists for that file. You still need a package built for your system.

Download sources FAQ

GitHub offers two ZIPs for Windows. Do I need both?

Choose one. The standard and PGO ZIPs in build 130 each contain a complete application. PGO describes how that copy was compiled. Keep its exact filename if you later compare performance or report a problem.

Which file should I hash if I already extracted the download?

Hash the original downloaded file, even if you have already extracted its contents. Compare the result with the SHA-256 shown beside that exact release asset on GitHub. A hash of lichii.exe alone covers different bytes and will not match the ZIP’s digest.

I downloaded an archive with a src folder and CMakeLists.txt. Where is the app?

Those are signs of a source archive. Return to the tag’s Assets list and choose the package with your OS and processor in its filename.