|
This article or section documents something not included in the current version of Scratch (3.0). It is only useful from a historical perspective. For information on the feature that replaced this one, see Project Compression. |
- This article or section documents an outdated version of Scratch (version 2.0). For this article in the current version (version 3.0), see Project Compression (3.0). For this article in Scratch 1.4, see Project Compression (1.4).
In Scratch 2.0, the maximum project size was 50 megabytes. If a project reached that limit and needed to be compressed, there were several ways to reduce size.
Sprites and Scripts
Projects could contain unneeded sprites and scripts, which could take up lots of space. This could be reduced by deleting the unneeded sprites or scripts.
Duplicate sprites could be deleted. Stamping or cloning could be used instead.
There may have been large actions that were repeated multiple times, which could take up lots of script space. This could be fixed by creating a custom block or using broadcasts.
Backdrops and Costumes
There may have been backdrops or costumes that were not being used. Deleting useless backdrops and costumes would free up space.
Bitmap images could be compressed. If they were from a local computer, they could be compressed externally and uploaded.
If a bitmap costume could be shown as a vector image, consider using a vector costume because vector images tend to take up less space.
If this was not possible, the image could be scaled down and back up, but that could cause unwanted pixelation.
Vector images could be further reduced in size by removing (and possibly replacing) excessive details such as windows on a building or fur on a hairy monster.
Sounds
Unused sound files could be deleted because they take up a lot of space. Common sounds to remove were the other sounds included by default in all sprites.
If your sounds were from your hard drive, then you can replace the sound with a compressed version.
