so maybe put it up for developers to fix it. its 2023 already and it's still the same problem. it should not have any limit, it's dumb and it's counter-intuitive and it's not that much of a code to implement.
Designing an Instagram carousel, for instance. IG allows 10 images in a carousel; at 1024px wide, that's over 10k pixels. The slice tool makes it super easy to split that design up, but then you can't output the slices with Save for Web. Yes, it's one workflow, and there are ways around it, but Slice tool + S4W is so convenient.
@flysi3000wrote: Designing an Instagram carousel, for instance. IG allows 10 images in a carousel; at 1024px wide, that's over 10k pixels.
"Save for Web (legacy)" is from ImageReady, which was released in 25 years ago in 1998. When was the Instagram Carousel developed?
In my (personal) opinion, it would be better for Adobe to create something new and exciting that would wow today's users instead of trying to fix Save for Web (legacy).
Aw man, I miss ImageReady! (lol, not really, but I did rely on it wayyy back in the day...)
Anyway, sure, a new tool would be great. It doesn't have to be an update of S4W, but something that fits today's workflows. Adobe would probably say use Adobe Express - maybe that's a valid option too. I got this particular example from watching an experienced creative director's frustration with trying to make a simple IG Carousel in Photoshpo. I think he's moved on to Figma.
Designing an Instagram carousel, for instance. IG allows 10 images in a carousel; at 1024px wide, that's over 10k pixels. The slice tool makes it super easy to split that design up, but then you can't output the slices with Save for Web. Yes, it's one workflow, and there are ways around it, but Slice tool + S4W is so convenient.
It isn't a matter of needing 8200px web images. It's about slicing individual, smaller images from one large design. It is ridiculous that individual slices are forced into final image sizes smaller than the actual size just because they are part of a single large file. Our "designers" are building files for mobile web pages that are way, way over the 8192px height limit. The web page consists of several sections that need to be exported individually. I now need to split the file into multiple, smaller files just so I can slice it and export the images at actual size. It's making for needless additional work. The whole point of slices and "Save for web" is to export a large layout into smaller assets. The size of the entire file should not limit the size of exported assets.
Adobe - remove the 8192px limit for "Save For Web".
As Save for Web (Legacy) is from the old ImageReady code-base, I doubt that it will be overhauled (I believe that it has had minor bug fixes and updates).
Slicing images to reassemble in an HTML table is mostly an outdated practice by current standards and technology (or so I am told).
Probably better to create a new idea topic for Export As to include/support slicing (I'll add my vote), as Export As is meant to replace Save for Web... Export As has some nice new features that are not available to Save for Web, however, it's also missing many other features from Save for Web. Unfortunately, Export As appears to be lagging in development since it's initial introduction.
NOTE: Even the new Export As has a limit of 20,000 px as the input size.
Until then, you are best using one of the scripts that I previously linked to save slices (PSD or JPEG) or make layers from slices.
112
Replies
AdChoices
