Export Settings for Lightroom: Presets by Destination (2026)

You've finished the edits, the gallery looks right on your monitor, and now you're staring at the export dialog wondering why the same file needs to go to Instagram, a client gallery, and a print lab in three different sizes. That's the normal state of things, not a sign you've missed a secret setting. The right export settings for Lightroom depend on where the file's going, what that destination does to it after upload, and whether anyone will edit it again. Build one preset per destination, test the published or printed result, and you'll stop re-exporting the same shoot three times to fix avoidable problems.

Which Lightroom Export Settings Fit Each Destination?

Use this table to find your destination first, then read across for format, color space, size, and quality.

Destination Format Color space Size Quality or resolution
Instagram feed JPEG sRGB 1080 px wide; 1080 × 1350 for 4:5 Quality 90 to 100, no enlarging
Personal website or portfolio JPEG sRGB 2048 px long edge Quality 80 to 90
Client proofing gallery JPEG sRGB 2048 px long edge Quality 90 to 100
Lab print, prepared by the lab TIFF or JPEG As the lab specifies (sRGB or Adobe RGB) Full size 16-bit TIFF; 240 to 300 ppi unless the lab says otherwise
Home inkjet print TIFF or JPEG Printer and paper profile (Adobe RGB or sRGB) Full size 180 to 480 ppi; soft proof first
Stock agency JPEG Agency spec, usually sRGB Full size or the agency minimum in its contributor guide Quality 90 to 100 at the agency's stated file-size limit
Archive or master DNG or TIFF Keep the original profile Full size Lossless; no quality setting

How to Read the Rows

The size column controls display size and file weight. A 2048-pixel file and a 6000-pixel file look identical in a small gallery slot, but the larger one uploads slower and gives the platform more work to undo. The quality column controls compression, not resolution. Lower quality throws away more data to save space, which is fine for a fast-loading portfolio and wrong for a file a client will print large.

Color space has to match what the destination accepts. Screens and most online services expect sRGB. Print work may use a wider space or a specific printer profile, but only when the lab or printer can use it. Sending a wider-gamut file to a service that assumes sRGB doesn't preserve more color. It usually misrenders it.

There's no single best row because Lightroom is built to produce different copies for different jobs. Adobe documented Lightroom Classic presets that show the two extremes: Burn Full-Sized JPEGs exports sRGB JPEGs at maximum quality and 240 pixels per inch, while For E-Mail (Hard Drive) caps sRGB JPEGs at 640 pixels on the width or height, at medium quality and 72 pixels per inch. Treat the first as a general-purpose reference and the second as a reminder of how small a pure display file can be.

Pick the row for the destination you deliver to most often and build that preset first. Add the others only when you actually send work there.

I would start with your website or client gallery preset if that's where most of your work lands, then add Instagram and print. An archive master is different in kind, not just size. Keep it full resolution and lossless so every future export starts from clean data, not from a JPEG you made for social media last year.

How Do You Build a Reusable Lightroom Export Preset?

Build the preset in the order of the Lightroom Classic export dialog, so sizing and sharpening act on the final pixels you'll deliver.

The Nine Steps in Dialog Order

  1. Set Export Location: Send each destination to its own folder, such as Web, Instagram, or Print. Exported copies should never sit beside your masters where you might edit the wrong file later.
  2. Set File Naming: Use a consistent pattern with the shoot name and a sequence number. You'll thank yourself when a client quotes a filename back to you months later.
  3. Choose File Settings: Pick JPEG for screen delivery and set quality to match the job, 80 to 90 for a personal website and 90 to 100 for client proofing or print delivery. Quality 100 rarely shows any visible gain on screen. It mostly inflates file size.
  4. Select the color space: Choose sRGB for any screen destination. Adobe's save and share guidance for Lightroom ties the color space to the intended output, and Lightroom accepts a long edge of up to 65,000 pixels, far beyond anything a screen needs.
  5. Set Image Sizing: Tick Resize to Fit, choose Long Edge, and enter 2048 for web or 1080 for Instagram. Keep Don't Enlarge ticked so small crops aren't upscaled into soft files.
  6. Set Output Sharpening: Choose Sharpen For Screen and Amount Standard for online work. Check the result at 100 percent, since sharpening that looks fine in a fit-to-window preview can look crunchy at actual pixels.
  7. Choose Metadata: Select Copyright Only for most screen exports. The file carries your copyright without handing over camera details, location data, or keywords you didn't intend to publish.
  8. Decide on Watermarking: Leave it off unless the destination is a proofing context where a mark serves a purpose. A watermark baked into a final delivery can't be removed without re-exporting from the master.
  9. Save the preset: Click Add in the Preset panel and name it for destination and size, such as Web 2048 sRGB. A clear name prevents the classic mistake of running a print batch through a social preset.

Two Pitfalls to Avoid

Don't confuse pixels per inch with delivered image size. For online use, pixel dimensions are what control display size and file weight. Changing 72 to 240 ppi without changing pixel dimensions adds no screen detail at all, because the browser or app doesn't use that number to lay out the image.

Don't export Adobe RGB or ProPhoto RGB to a service that expects sRGB. A wide-gamut file that arrives untagged or unsupported can display with shifted or muted colors, which readers often misdiagnose as a Lightroom editing problem. The edit is usually fine. The tag is wrong for the destination.

Practical rule: Export three test files and open them in a non-Adobe viewer before you trust a new preset with a full batch.

Check dimensions, embedded profile, orientation, metadata, and file size on those tests. A viewer outside Adobe's ecosystem shows you what recipients see, without Lightroom interpreting things in your favor. Once the tests pass, the preset removes a dozen decisions from every future batch, and consistency stops depending on whether you remembered a checkbox at midnight.

What Size Should You Export for Instagram and the Web?

Social platforms decide the final pixels, whether you plan for it or not. Instagram's official photo upload guidance states that photos are retained at their original resolution when their width is between 320 and 1080 pixels and their aspect ratio falls between 1.91:1 and 3:4. That means a 3:4 portrait can reach 1080 × 1440 pixels, while a 1.91:1 wide image is approximately 1080 × 566 pixels.

Let the Platform's Ceiling Set Your Export

Files narrower than 320 pixels get enlarged, and files wider than 1080 pixels get reduced. Exporting a camera-native file doesn't beat that ceiling. It just hands the resizing and recompression decisions to the platform instead of making them yourself in Lightroom, where you control sharpening and crop.

Crop is where this gets expensive. Say you've shot a 3:2 photo orientation and want it in a 4:5 feed slot. That crop keeps only about half the original width, so a subject near the edge can end up clipped or awkwardly tight. Make that decision yourself with the Crop tool before export, and use a virtual copy for each ratio so your master edit stays intact. If you're unsure how resizing interacts with detail, work through how to resize an image without losing quality before you lock your presets.

Recompression Changes What Matters

Platforms recompress what you upload, so the Quality slider matters less than getting the crop right, supplying enough pixels, and tagging the file sRGB. Pushing quality to maximum on an oversized file mostly gives the platform a bigger file to recompress. If you want platform-side tactics that pair with a clean export, Sup Growth, an Instagram growth-service vendor, has a walkthrough on how to reduce Instagram photo compression is a useful companion once your dimensions are already correct.

Publish one test post and inspect it at full size on a phone. That's the file your audience sees, not the tidy preview on your desktop. If it looks soft or the colors have shifted, re-export from the master with corrected settings rather than re-uploading a copy that's already been compressed once. Each extra compression pass costs detail you can't get back.

A 2048-pixel long edge still suits portfolio websites and galleries that display images larger than a phone feed. It gives high-density displays something to work with without the upload weight of a full-resolution file, and it degrades gracefully when a content delivery network generates smaller versions from it.

Which Settings Should You Use for Print Exports?

A lab asks for a print file and gives you no profile, no size, and maybe just the words "high res." That vagueness is the problem, not your export dialog.

PPI Is a Label, Not Detail

Print size comes from pixel dimensions divided by ppi. Take a hypothetical image that's 3000 pixels wide. At 300 ppi it prints 10 inches wide. At 240 ppi it prints 12.5 inches wide. The pixels are identical in both files. Only the instruction about how densely to place them has changed, so raising the ppi number on a small file doesn't create detail that was never captured.

That's why 300 ppi should be treated as a common lab request, not a guarantee of a better print. A file with genuine pixels to spare will print well at a range of settings, and a file that's short on pixels won't be rescued by a metadata value. Viewing distance matters too. A large print viewed from across a room needs less density than a small print examined in someone's hands.

Profiles, Soft Proofing, and Double Management

Ask the lab for the ICC profile for the exact printer and paper combination you'll be printed on. Photo Review's soft proofing guidance describes a properly color-managed workflow using that exact profile, followed by soft proofing for gamut and brightness limitations. In Lightroom, soft proofing with the profile shows you which saturated colors the paper can't reproduce and whether shadows will block up, while you can still adjust the edit instead of paying for a reprint.

Watch for double color management. If Lightroom converts the file using the lab's profile and the printer driver then applies its own correction, the colors get adjusted twice and they shift. One application manages color, or the other does. Never both. Our deeper walkthrough on choosing a color profile for printing covers how to tell which side should own that job for a given lab.

A Short Decision List

How Should You Export for Stock and Clients?

Stock and client work often use the same JPEG at the same size. What differs is the metadata inside it and how you stage the delivery.

Stock Agencies Write Their Own Rules

Each agency publishes its own size, color space, and file-size requirements in its contributor guide. Copy those exact values into your preset rather than assuming one agency's rules match another's. If a value isn't stated, ask or check the guide before a batch upload, since rejected files cost more time than reading the spec does.

Set title, keywords, and copyright in Lightroom's Metadata panel before export, then choose a metadata option that keeps them, such as All Except Camera Raw Info. Using Copyright Only here would strip the keywords the agency's search depends on. Keep in mind that model and property releases are separate documents you upload alongside the image. They're not metadata fields, and no export setting substitutes for them.

Client Work in Two Tiers

Deliver clients in tiers. The first tier is a 2048-pixel sRGB JPEG at quality 90 to 100 for the online proofing gallery, large enough to judge focus and expression on any screen. The second tier is the full-size set for print, exported after the client has approved their selections.

Say a wedding photographer finishes a shoot with a few hundred keepers. She exports the gallery set first so the couple can make selections quickly, then runs the full-size batch only for the approved images once final payment clears. That sequence saves hours of rendering and gigabytes of uploads on files nobody chose.

Name files so they sort and identify themselves, with client name, shoot date, and sequence number, such as SmithWedding_2026-06-14_0231.jpg. When a client emails asking for "that one from the ceremony," a searchable filename turns a scavenger hunt into a ten-second lookup.

How Do You Fix Color Shifts, Soft Files and Oversized Exports?

When an export goes wrong, you arrive with a symptom, not a setting. Match what you're seeing to a likely cause before you start moving sliders at random.

Symptom Likely cause Fix
Colors shift after upload Adobe RGB or ProPhoto RGB sent to an sRGB-only service Re-export in sRGB with the profile embedded
Image looks soft on a phone Long edge too small, or platform resized the file Export 1080 px wide for Instagram or 2048 px for web; check at 100 percent
Print looks darker than the screen Double color management, or no soft proof Use one color manager, the lab's ICC profile, and soft proof before printing
File exceeds the upload limit Quality 100 at full size Lower quality to 85 to 90 or reduce the long edge; remove unneeded metadata
Crop is wrong on the platform Crop applied after export, or ratio outside 1.91:1 to 3:4 Crop in Lightroom before export and check the ratio
Print size unchanged after changing ppi Ppi is a label; pixel count did not change Change pixel dimensions or print size, not ppi alone
Metadata missing after upload Metadata set to none, or platform stripped it Set metadata to Copyright Only or All Except Camera Raw Info and test one upload

Why the Local Preview Misleads You

The most common complaint is color that shifts after upload, and it almost always traces back to a wide-gamut file landing on a service that assumes sRGB. The second most common is softness, which usually means the exported long edge was too small for the display slot or the platform resized a much larger file using its own method.

Underneath every row sits the same validation habit. A platform may recompress, resize, or strip metadata from what you upload, so the published or printed result is the only reliable check. Your local export preview tells you what left your computer. It says nothing about what the destination did next.

If you haven't looked at the uploaded version on the device your audience uses, you haven't checked the export yet.

Before any batch runs, open test files in a non-Adobe viewer and confirm dimensions, profile, orientation, metadata, and file size. Portrait images that arrive rotated, files that lost their copyright, and exports that are five times heavier than the upload limit are all cheap to catch on three test files and expensive to fix across a full shoot.

Why Should You Test One Export Before the Batch?

You don't need seven presets today. You need the two or three you'll use this week, tested properly.

  1. Name your top destinations: Pick the two or three places your files go most often.
  2. Build one preset each: Follow the nine-step sequence and name every preset for its destination and size.
  3. Export three test files per preset: Check them in a non-Adobe viewer for dimensions, profile, and orientation.
  4. Upload or print one test: Inspect the published or printed result at full size, then adjust the preset if it misses.
  5. Keep one master untouched: Every preset should be rebuildable from a clean original.

For repeat work across a whole shoot, pair these presets with a consistent approach to batch edit photos so the edits feeding your exports are as uniform as the exports themselves. If you also work outside Lightroom, note that RevelRaw does not import the Lightroom catalog, though compatible Lightroom .xmp presets and .cube color LUTs can be imported into a personal look library where they can be renamed and reordered, and a photo's crop and straighten angle come across from its .xmp sidecar. Adobe profiles and Lightroom masks do not, and rendering can differ. Its Instagram export preset, for reference, is JPEG, 1080 × 1350, sRGB, 90%, and like every RevelRaw export preset it keeps the crop's shape and never enlarges.

These steps apply to any export tool you use. A second application earns a place in your workflow only after it passes the same test on a sample batch, one published file checked at full size.

Frequently Asked Questions

What are the best Lightroom export settings for Instagram?

JPEG, sRGB, 1080 pixels wide with Don't Enlarge on: 1080 × 1350 for a 4:5 portrait or 1080 × 1080 for a square. Quality 90 is plenty, because Instagram recompresses every upload. Crop to the ratio in Lightroom before export so you control the framing.

What resolution should I export for print from Lightroom?

Export full size and follow the lab's request, often 240 or 300 ppi. The ppi value only labels how densely pixels are placed; print size comes from pixel dimensions divided by ppi, so raising ppi on a small file adds no detail. Ask the lab for its ICC profile and soft proof before exporting.

Should I export in sRGB or Adobe RGB from Lightroom?

sRGB for anything viewed on a screen: web, social, email and client galleries. Adobe RGB or a printer profile only for print workflows that ask for it. A wide-gamut file sent to a service that assumes sRGB usually looks muted or shifted.

How do I save Lightroom export settings as a preset?

Set every section of the Export dialog, from location and naming to file settings, sizing, sharpening, metadata and watermarking, then click Add in the Preset panel and name it for the destination and size, such as Web 2048 sRGB. Test three files from each new preset before using it on a whole shoot.

Can I use my Lightroom presets in RevelRaw?

Compatible Lightroom .xmp develop presets and .cube LUTs import into RevelRaw's look library, and a photo's crop and straighten angle come across from its .xmp sidecar. Lightroom catalogs, masks and Adobe profiles do not import, and rendering can differ. RevelRaw requires macOS 26 or later on an Apple M1 or later Mac.


Export presets are only half the job, so we built RevelRaw as a native macOS RAW editor with destination presets for social, web, stock, and print that set format, dimensions, quality, and color space together, processing on your Mac with no account and no uploads. If you're a Lightroom user who wants account-free editing and can bring compatible presets and LUTs along, download it free, run one shoot through it with the included full-quality export, and judge it by the same test you'd apply to any export. It requires macOS 26 or later on an Apple M1 or later Mac.