Mahjong

Switch from browser mahjong

By Porcelain Lattice editorial team Current release, published September 12, 2026

Framed tile-pair panel with umber tile faces and sand pips on tile-mist paper.
Tile-pair panel: matching tile faces used as the mahjong mark across this install guide. Porcelain Lattice original tile-pair geometry for factory-mahjong (not an ffalt/mah logo).

Moving off a browser mahjong portal means installing Mah from GitHub Releases, proving a local clear, and keeping the old bookmark only as a fallback.

Browser portals are fine for disposable tabs. They fail when you need a durable binary, local auto-save claims, and a filename you can put on a ticket. Mah answers those needs under MIT.

What transfers

Skill transfers. Portal streaks and ad-account progress usually do not. Expect to rebuild daily-challenge habits inside the local client after install.

  • Install from Releases, not from the portal’s “download” button
  • Prove one local clear before you remove bookmarks
  • Keep the browser site as optional play, not as the installer

Steps

  1. Install Mah. Prefer win-mah-*-x64.msi on Windows, or the matching DMG or .deb for your OS.
  2. Clear one board. Use a classic layout such as Turtle or Dragon before you chase themes.
  3. Optional daily challenge. Turn it on only after the first clear works.
  4. Retire the portal download links. Keep play bookmarks if you want, but stop using portal installers.

Why people switch

Fewer adware surprises, clearer update doors, and a client whose README claims no ads, no tracking, and no cloud. Comparison: vs browser mahjong.

Limits

A desk install does not recreate every portal skin. It does recreate a mahjong solitaire loop you control. Safety: is it safe.

Porcelain Lattice maps filenames for people who searched for a local mahjong client and need an MIT Mah path. Upstream remains at ffalt.github.io/mah and ffalt/mah under MIT.

  • Keep one installer door forever on each machine ticket.
  • Prove one short local clear after every reimage.
  • Ask for the GitHub Releases URL instead of vague “best download” links.

Why filenames beat portals

People searching for mahjong often land on advertising pages that wrap a browser game or a renamed installer. Those pages can change overnight, hide the real filename, and ship toolbars beside the setup you thought you chose.

  • Prefer win-mah-*-x64.msi on Windows from ffalt/mah Releases
  • Prefer the aarch64 DMG or amd64 deb on the same tag when those desks matter
  • Refuse Softonic-style mirrors that hide the filename

No winget package id was found on this review date. Inventing one would send shared labs to the wrong mahjong product.

Repeatable lab rhythm

Club machines, classroom images, and family PCs all benefit from the same boring checklist. Write the OS version beside the asset name. Prove one short mahjong clear after every reimage.

  1. Match the GitHub filename character for character.
  2. Launch Mah and prove a local clear.
  3. Document the update door on the machine ticket.

Travel bags should separate phone apks from desk MSI files so a hurried restore never grabs the wrong binary. Shared tickets should say whether the room standard is deb or AppImage on Linux.

Closing discipline

Ask for the GitHub Releases URL whenever someone pastes a vague “best download” link into chat. Match characters in the filename. Prove a clear. Document the update door for this mahjong client.

Asset checklist before imaging

Before you image a lab for mahjong, confirm the live Releases tag still lists the Windows primary MSI together with the Linux and macOS builds you need. Prefer one tag for every desk in the room so support tickets stay short.

  • Windows: win-mah-*-x64.msi (EXE alternate on the same tag)
  • macOS Apple silicon: macos-mah-*-aarch64.dmg
  • Linux: linux-mah-*-amd64.deb or AppImage or rpm

Android apks help travel phones, yet they do not replace the desk MSI when you rebuild a shared mahjong image.

Support ticket lines that work

Write three lines on the machine ticket: OS version, exact asset filename, and the date you proved a local clear. That record beats another Softonic search when SmartScreen returns next month.

  1. Record the GitHub Releases URL you typed.
  2. Record the filename character for character.
  3. Record “cleared one board” with the date.

Family PCs and classroom images both benefit from that boring mahjong paperwork. It keeps the next bump on the same honest door without inventing a winget id that was not found.