Pixel art on GitHub

The open-source project behind this pixel art install is LibreSprite/LibreSprite. README, LICENSE.txt (GPL-2.0), SECURITY.md, and Releases all live there. This guide is independent; it does not speak for the project.

Home: pixel art. Releases detail: releases.

What to open first

Start at the repository README for features, then open Releases for binaries. INSTALL.md covers compiling from source if you need that path. Most readers only need the Windows zip.

Licence and history

LibreSprite forked the last GPLv2 commit of Aseprite after that project moved to a proprietary licence. Cite the README history section when you explain why a free pixel art zip exists beside paid editors. Compare: vs paid sprite editors.

Security contact

SECURITY.md asks you to file GitHub issues with OS details and screenshots, with Discord and Reddit listed as fallbacks. Safety guide: is pixel art software safe.

Stars and activity

Star and push dates shown in the install panel come from the live fetch. Do not hard-code them in prose. Treat them as freshness signals, not as proof of safety alone.

Issues and contributions

Product bugs belong on the upstream issue tracker. Install guide mistakes belong on this site’s contact process. Contributing.md explains how to help the project itself.

Resources and theming

Theming packs and related resources are linked from the project site and Theming.md. They are optional after a working pixel art extract. Palettes guide: palettes and layers.

What this overview skips

Binaries are not mirrored here. Every download still points at GitHub Releases. Download-safe rules: download safely. Windows install: install on Windows.

Bookmark set for labs

• Repo root for licence and README.
• Releases list for the Windows zip.
• SECURITY.md for vulnerability reports.

With those three bookmarks, a shared desk can reinstall pixel art tools without searching random blogs.

README features that matter for install guides

Upstream lists real-time animation previews, onion skinning, multiple sprites, palettes, layers and frames, tiled drawing, and several file types. Those bullets explain why a local pixel art install still matters compared with a one-tab doodle. They are not a marketing rewrite; they are the project’s own summary.

Compiling versus downloading

INSTALL.md is for people who want to build from source with CMake and platform dependencies. Most readers of this cluster should stay on the Releases zip. Mention compile docs only when a ticket explicitly requires a custom build. Windows install: install on Windows.

Community channels without redirecting install

Discord, Matrix, and Reddit links appear in project docs for community help. They are not download mirrors. Keep binaries on Releases even when a helpful stranger offers a Drive folder in chat. Download-safe: download safely.

Fork awareness for support tickets

When a student pastes an error, confirm they run LibreSprite from this repo’s zip, not a differently named fork or a paid proprietary build. Ticket language should say pixel art editor extract path plus the GitHub repo URL. Releases: releases.

Liberapay and optional tips

The README links a Liberapay tip jar. Tips are optional and do not unlock the zip. Do not describe tips as a required licence fee. Free versus paid seats belong on the comparison pages.

Editorial distance

Sprite Quill publishes install guidance. It does not claim ownership of the code, trademarks, or screenshots beyond fair use of GPL assets credited on figures. About: about. Editorial method: how we verify.

First run: first run. Zip extract: zip extract. Update: update and uninstall. Palettes: palettes and layers. Animation: animation basics. Vs paid: vs paid editors. Vs browser: vs browser toys.

Practical notes for helpdesk staff

When a ticket says the pixel art window will not open, ask for the extract path screenshot first. Most failures are missing data folders or blocked exes, not missing features. Confirm the zip came from GitHub Releases before you escalate. Point the reporter at the home pillar and the download-safe page so they can self-check the URL shape.

Keep language plain on the ticket: name the zip, name the exe, name the folder. Avoid brand-first shortcuts that skip extract steps. After a fix, ask for one saved sprite as proof. That closes the loop faster than a vague “please try again later” reply and keeps the next volunteer from repeating the same mirror mistake.

Staff can also keep a known-good USB extract labelled with the tag and zip filename. That stick is for emergency restores only after the networked Releases fetch fails. It is not a reason to skip documenting the official URL on every machine image you ship this term for pixel art labs.