Fantyzo

Fantyzo support

Find help. Keep your secrets private.

Start with your version, operating system, and the exact error you see.

Manuals and release information

Before you capture

The public 2.3.2 screenshot path creates a public Catbox link. Do not use that workflow for content you intend to keep private. Pro 2.4.0 Cloud is in development and uses a separate authenticated private path.

Windows downloads

Download only from the official site. If a warning appears, verify the source and compare the file against published SHA-256 checksums. Do not disable security software to troubleshoot an unexplained warning.

Linux capture

The available .deb targets Linux Mint 22.x and Ubuntu 24.04 using an Xorg/X11 session. Confirm that your session is X11 when region capture or global hotkeys do not work. Install the package from its download directory with sudo apt install ./fantyzo_2.3.2_amd64.deb.

Pro sign-in and private access

In the development client, sign in using your Fantyzo username and password, then enter the current six-digit authenticator code. If a code is rejected, check the authenticator device’s time and try a fresh code. If the login session expires, sign in again.

A private Cloud object address is not a public URL. An authentication error does not mean the screenshot was published or deleted. Browser access and public Share controls are still being developed.

Storage and upload errors

If an upload is refused because your quota is exceeded, existing Cloud files are retained. Free enough space or increase the allowance when the option is available. If Pro entitlement has ended, consult the 30-day recovery policy.

History cleanup

Deleting or clearing History in 2.3.2 removes local entries and previews, not the image hosted on Catbox. A local cleanup action must not be confused with Cloud file deletion either.

Getting more help

For the available in-world contact point, visit Imagine Foundry in Second Life. A dedicated web support contact and account recovery workflow will be listed here when available.

Include your Fantyzo version, operating system, what you tried, and the error text. Remove private content from screenshots. Never send passwords, authenticator codes, recovery secrets, or session tokens.