Peneren wrote:

Support, for the following reasons:
1. Assets are already 10MB, and you can upload almost as many as you want, meaning that even just adding 1 10MB asset will already be roughly twice the size of project.json, and thats just 1 asset.
2. Most projects don't reach the 5MB project.json limit anyway, meaning that this won't really impact server performance drastically
3. The existence of this limit inhibits the creation of impressive projects, removing it would help the few people who do hit the limit actually create the projects they want

I agree

michaeljackson1365 wrote:

1159661667 remember this number
Every project has a .json file of 5 mb. Since there are about 1159661667 projects, this adds up to 5.7 PETABYTES of data. That's only for .json storage for each project
Multiplying the number by 2, and you get 11.5 petabytes. That's the storage capacity for all images, files, sounds, etc.
Adding both, that's 17.3 petabytes of storage.
But adding a sixth megabyte can make the servers run out of storage faster, meaning 6.9 petabytes of storage for every project (total storage), or 1.15 petabytes if the .json file size was raised by a megabyte/project.
Even though this suggestion was from 2021 and whoever wrote OP is probably gone, I still find this interesting. No support.

The problem with this is that it assumes every project is 5 mb, when the size of a project is in fact variable since it's really just a fancy .zip file. Most of the projects on Scratch are probably only kilobytes in size.
For example, the default TurboWarp project is only 2,438 bytes large. Multiply that by 1159661667 and you get merely 2.8 terabytes.
While this is definitely NOT the full size of the entire Scratch project database, it is most likely somewhere in-between those two numbers.
Of course not everyone will use this feature, but those who do won't inflate the size by very much in the grand scheme of things.