Nomado Apps / Blog / Wedding photo sizes for client galleries, blogs and Instagram
Wedding photo sizes for client galleries, blogs and Instagram
One export size rarely fits every place a wedding photo ends up. Here are sensible starting points for each, and why the file size matters as much as the pixel size.

Pixel size and file size are different things
Pixel size is how many pixels wide and tall a photo is, usually given as the long edge. File size is how many megabytes it takes on disk. Two photos with the same long edge can differ several times in file size, depending on the JPEG quality setting, the amount of detail and noise, and how efficiently the file was encoded.
For delivery you need to decide both: a pixel size that suits where the photo will be seen, and a file that is no heavier than it needs to be at that size.
Starting points for each use
These are practical defaults rather than rules. Check the guidance of your gallery provider and your website theme, which may recommend their own sizes.
- Export for the web in sRGB. Not every browser, app and screen handles other colour spaces the same way.
- Instagram has shown feed photos at 1080 pixels wide for many years. Uploading much larger files does not make them sharper there.
- Many gallery services make their own smaller display versions from what you upload, so full size uploads there are fine. Your own website usually does not, so size images before they go up.
- Keep your full size masters. You can always make a smaller copy later, but never a larger one.
| Use | Suggested long edge | Why |
|---|---|---|
| Full resolution download for the couple | Full size | Keeps every option open for prints and albums |
| Online gallery viewing | About 2048 px | Sharp on large and high density screens without very heavy files |
| Blog posts | About 1600 to 2048 px | Roughly twice the width of the text column, so it stays crisp on high density screens |
| Social media | About 1080 to 1200 px wide | Platforms resize and recompress uploads, so larger files gain little |
| Email and quick previews | About 1200 px | Small enough to send and open quickly |
Why file size matters for page speed
On most wedding websites and blog posts the photos are the heaviest part of the page by far. A page full of 8 MB exports takes much longer to load on a phone than the same page with files a fraction of that size, and visitors on mobile data notice.
Search engines also measure loading speed. Google's Core Web Vitals include Largest Contentful Paint, which on a photography page is very often the first large photo. A lighter hero image helps that measure directly.
Galleries benefit too. Smaller files upload faster from the studio, take less storage, and open more quickly when the couple and their families browse on their phones.
- Resize to the size the page actually shows, with a version for high density screens.
- Compress each file as far as it can go without a visible change.
- On your own site, load photos below the first screen lazily and keep the first large photo loading straight away.
How visually lossless compression works
JPEG compression throws away detail the eye is least likely to notice. The quality slider decides how much. Most editors default to high settings for safety, which often leaves a lot of size that could go with no visible difference.
Visually lossless compression looks for the smallest file that still looks the same as the original when you compare them. Doing that well needs a way to measure what a person would see, not just a fixed quality number, because the right setting depends on the photo. A dark reception shot with smooth gradients needs more care than a bright, detailed portrait.
- JpegSlim encodes each photo at many compression levels with the mozjpeg encoder.
- It scores every 512 px tile of each attempt with SSIMULACRA2, a modern visual quality measure. On its published scale, 85 means no difference noticed when the two images are compared in place at 1:1, and 90 means none even when flicking between them at 1:1.
- It keeps the smallest file in which every tile scores at least 88 with the default High quality preset. Checking every tile rather than an average is what protects skies, skin and dark corners from banding.
- If a photo cannot get smaller, the original is copied unchanged, so the output folder is always complete. Files are never made larger and all metadata stays.
In the developer's tests on a scan and synthetic test set, the High quality preset made exports saved at quality 98 to 100 roughly 50 to 70% smaller, camera JPEGs at Fine about 20 to 35% smaller, and files already saved at quality 90 or below about 10% smaller. Real camera files with high ISO noise usually shrink somewhat less.
A simple delivery workflow
- Export full size JPEGs from Lightroom Classic or Capture One at high quality.
- Make every delivery size from those exports in one pass. In JpegSlim, tick the output sizes you need, for example Full size, 2048 px and 1200 px, and each goes to its own folder.
- Upload the full size or 2048 px folder to the client gallery, the 2048 or 1600 px versions to the blog, and the 1200 px versions to social media.
- Spot check a few photos side by side with the originals at 100% before you send anything.