Photoshop still exports the best images on a web page and it is no longer where screens get designed. Use it for the photograph, the hero, the thing with pixels in it, and take the layout somewhere that can change a screen without rebuilding it.
Nadia builds the image side of a hotel site in Alexandria: fourteen rooms, one hero, a gallery, and a page weight the client's own agency measures every Monday.
Set the document up once and it stays right
Work in sRGB and 8 bits per channel, and convert to sRGB on the way out. A file left in Adobe RGB looks correct in Photoshop and washed out in every browser, and the discovery always happens after the images are on the server.
Before exporting a pixel
Three setup habits that stop browser colour shifts
Colour profile, bit depth, and artboard naming are decided once at document creation rather than fixed after upload.
- 01Set document to sRGB and 8 bits per channelAdobe RGB looks normal inside Photoshop and washed out in every browser
- 02Create one artboard per target viewportUse 1440 for the desktop hero and 390 for the mobile frame
- 03Name the artboard after the final assetNaming it room-gallery instead of Artboard 1 produces the right filename automatically
Converting to sRGB on export catches anything missed earlier, so the server never receives an Adobe RGB file.
One artboard per deliverable, sized to the real thing: 1440 for the desktop hero, 390 for the phone. The artboard name becomes the file name, so name it room-gallery rather than Artboard 1 and the export is already correct.
Three formats, and the choice is not a preference
PNG for flat colour and transparency, JPEG for photographs. A photograph as a PNG is roughly ten times the bytes for a difference nobody has ever seen; a logo as a JPEG has a grey fuzz around every edge.
Three web formats
Format follows pixel content rather than habit
Choosing between PNG, JPEG, and WebP depends on whether the image carries flat edges or photographic tone.
Web image export
- Flat colour and transparencyLogos, wordmarks, and sharp UI graphics
- PNG keeps crisp edges without grey compression fuzz
- Photographs and hotel roomsContinuous tone where PNG balloons roughly tenfold
- JPEG at quality 60 balances detail against blocky skies
- WebP shrinks files further with full browser support since 2020
Photoshop writes WebP natively, which turns a forty-photo room gallery from a slow stall into a fast load on hotel wifi.
Export photographs as JPEG at quality 60. Above that the file grows and the image does not improve; below it the sky goes blocky first, which is the thing to look at when checking.
WebP is smaller than both and every major browser has taken it since 2020. Photoshop writes it natively, and for a gallery of forty room photographs it is the difference between a page that loads on hotel wifi and one that does not.
Two sizes, always
Export at the size the image is displayed, and again at twice the pixels. The first is what most people download and the second is what a modern laptop screen needs to look sharp, and the browser picks between them.
Monday page weight check
Same hero dimensions, fifteen times the file weight
Exporting at display size and twice the pixel density keeps sharp screens happy without shipping print-grade megabytes.
kilobytes for one 1440 by 600 hero image
Web JPEG at quality 60Unoptimised print export
- 1440 by 600 hero90 kB1.4 MBShipping the careless print export drives most of the agency's Monday page-weight complaint
Export two sizes together: 1x for standard displays and 2x so modern laptops stay sharp while the browser picks between them.
A hero at 1440 by 600 as a JPEG at quality 60 is about 90 kB, and the same picture exported carelessly out of a print file is about 1.4 MB. That single number is most of what an agency's Monday measurement is measuring.
Two shortcuts worth setting up
Name the layer with the extension and Photoshop writes the file: a layer called hero.jpg becomes hero.jpg in a folder beside the document, updated every time the layer changes. It is old, it is still there, and for a gallery it saves an afternoon.
Built-in automation
Two settings that remove manual export work
A layer extension rule and a single preference change keep a whole gallery updating cleanly on every edit.
- Name layers with a file extension
- Switch Quick Export away from PNG
- Name layers with a file extensionA layer named hero.jpg writes hero.jpg into a sibling folder and refreshes whenever the layer changes
- Switch Quick Export away from PNGChanging the default preference once stops photographic assets from exporting as oversized PNGs
Together these two settings turn a repetitive afternoon gallery export into a background folder sync.
Set the quick export format once, in preferences. The default is PNG, which for a site made mostly of photographs is the wrong answer on every single export until somebody changes it.
The part Photoshop cannot do
Photoshop has no inspect mode, so the handoff is a document you write. Nobody can click a layer and read a padding value out of it, which means every spacing decision has to be typed somewhere a developer will look.
Fourteen rooms, one hero
Which part of this page comes out of Photoshop
Three of these five parts are images and two are layout. Photoshop owns the three, and the two are why the file has to leave.
- 011440 by 600
- 02Sea View Double
- 03forty photographs
- 05a wordmark on transparent
- 01The heroa JPEG at quality 60 is about 90 kB, and the same picture out of the print file is about 1.4 MB
- 02The room namelayout, not image: it has a padding value somebody has to read, and Photoshop cannot be asked
- 03The galleryWebP, written natively, and the reason the page loads at all
- 04The booking buttonthe same button on fourteen pages, which is the thing a layer group cannot say
- 05The logoPNG, because a JPEG puts a grey fuzz around every edge of it
The parts marked as layout are not harder to draw here. They are harder to change here, and a hotel site is changed every week.
That is the honest reason this page is short on layout. Photoshop is where the image is made, and the screen it sits in belongs somewhere that measures itself.
What to open
Export As, in Photoshop as of 2026, replaces Save for Web, which is still in the file menu marked as a legacy item and still what half the tutorials show. There is no free tier. Export As is the one that writes WebP and does the two sizes in a single dialogue.
What to open in 2026
Photoshop makes the pixels; Figma holds the screen
The handoff problem disappears once image production and inspectable screen layout stop living inside the same file.
- Photoshop Export AsPaid tool with no free tier
- Replaces legacy Save for Web
- Exports native WebP files
- Writes 1x and 2x sizes in one dialogue
- Figma for layoutReal free tier available
- Replaces PSD spacing notes written in email
- Measures padding directly for developers
- Holds reusable buttons across all rooms
Clean division of labour
Use Photoshop strictly for photographs and heroes, then place the exported assets into a tool that measures itself.
Figma, as of 2026, replaces handing a PSD to a developer with the measurements written in an email. Its free tier is real. Photoshop makes the image and Figma holds the screen it goes into, and that division is the whole recommendation on this page.
Where it stalls: building screens here and then being asked to change one
Any single screen can be built in Photoshop, beautifully, in an afternoon. The trouble arrives on the second Tuesday, when the client wants the booking button larger on all fourteen room pages.
Where screen files stall
One client tweak reveals whether the layout belongs here
A static mockup looks effortless on day one, but repeating an edit across fourteen room screens exposes copied layer groups.
- Built as copied layer groupsFourteen manual editsRoughly three hours every Tuesday the copy changes
- No link between identical buttons
- Copied groups drift apart after four edits
- Every future change repeats the full three hours
- Built with shared componentsOne single component editAll fourteen pages inherit the updated size immediately
- Change the master button once
- Consistency holds across every room
- Photoshop keeps only the room photographs
The moment you copy the same layer group four times is the signal to move layout work out of Photoshop.
In a file made of layer groups that is fourteen manual edits and about three hours, and it is three hours again the next time. In a file made of components it is one edit. The person doing the fourteen concludes they are slow, and they are not: the file has no way to say that those fourteen buttons are the same button.
The tell is copying a group and moving it. Somebody who has copied the same group four times has built four things that will never agree again, and that is the moment to move the layout out and leave the images behind.
What it looks like when it goes wrong
The gallery went live with forty photographs exported straight from the retouching file: full size, quality 100, Adobe RGB. The page came to 38 MB, the agency's Monday measurement went from four seconds to fifty one on a phone, and the hotel's booking form sat under all of it. Re-exporting everything correctly took about twenty minutes once somebody looked.
Alexandria gallery incident
How forty retouching exports buried the booking form
Shipping straight from master retouching settings turned a four-second mobile page into a fifty-one-second wait.
- Exported straight from retouchingFull pixel size, quality 100, left in Adobe RGB
- Page weight swelled to 38 MBForty oversized images stacked above the fold
- Mobile load hit fifty one secondsMonday agency measurement jumped from four seconds
- Booking form pushed belowVisitors waited on forty heavy files before reserving a room
- Fixed in twenty minutesRe-exporting to sRGB and proper web sizes restored normal speed
Once somebody checked the export dialogue instead of blaming the server, the entire thirty-eight megabyte mistake took twenty minutes to undo.
What produced the images in the first place is skin, objects and restraint, and the file structure that kept them editable is non destructive editing, and why it matters. The hero itself was assembled from three photographs, which is several images passing as one photograph. What the program is for altogether sits one level up, in pixels: retouching, compositing and screen design.