Skip to content

Scumble 0.1.51: large exports save again, and two new skins

Choose a tag to compare

@github-actions github-actions released this 24 Oct 01:44
· 734 commits to main since this release

Get Scumble

Package Download Size Notes
Microsoft Store (Windows) Scumble in the Store or winget install scumble – Signed by Microsoft and updated by the Store; a new version can reach the Store a few days after GitHub (Microsoft's certification).
Windows installer Scumble-Setup-0.1.51.exe 124 MB Updates itself; not code-signed yet, so SmartScreen asks once.
Windows portable Scumble-0.1.51-portable-win-x64.zip 174 MB No install: unpack and start Scumble.exe; keeps its data in a folder beside it and does not update itself.
Linux AppImage scumble-0.1.51.AppImage 152 MB Early build made by CI, not tested by the author yet.
Linux .deb scumble-0.1.51.deb 119 MB Early build made by CI, not tested by the author yet.
Claude Desktop extension scumble-0.1.51.mcpb 78 KB Adds Scumble's MCP tools to Claude Desktop with one click; needs Scumble installed (any of the above).

The other files of this release (latest.yml, latest-linux.yml and the .blockmap) are for the app's updater; you do not need to download them.


  • Large exports save again. Saving an export of more than about 500 MB (a PSD of a 15,000 x 10,000 picture with a layer above it is about 0.9 GB, and a large ORA or TIFF can pass it too) ended Scumble's window: it reloaded and brought the documents back from the autosave, but the file was never written. An export now goes to the disk in pieces, whatever its size.
  • Two new skins under Settings › Appearance (and View › Skin): Comfy, a deep aubergine night with neon-yellow pills, the side panel's sections as node cards with a yellow socket, and Black Forest, forest-night greens with warm cream type, sage accents and calm rounded panels.
  • An export is written to a temporary file beside the target and put in its place only once every byte is written, as a .scumble document is: a save that fails, or a disk that is too full for it (now said before anything is written), leaves an older file of the same name as it was. When another program holds that file open (a viewer), or the file has other names (a hard link), the export is written into it as before; a symbolic link keeps pointing at the new picture. A read-only target is refused before the export is written.