Export photographs for their destination instead of a vague idea of quality
Keep a master, make a purposeful delivery copy, and check what actually reaches the viewer.

Start with the place the picture will appear
The export dialog often arrives at the end of a long editing session, when attention is already running low. It asks about dimensions, format, compression, color, sharpening, and metadata as if these were independent technical preferences. They are better understood as delivery decisions. A family print, an email attachment, and a website thumbnail can all begin with the same original while needing different output files.
Before exporting, write down the destination and any published requirements. A print lab may specify dimensions or a preferred color workflow. A website may resize uploads automatically. A collaborator may need a full-size file for a layout rather than a finished small image. If the destination has clear instructions, follow them instead of guessing from a generic online recipe. Export quality is partly about compatibility with the next step.
Keep the original and editable work separate from delivery copies. Repeatedly opening a small compressed export and saving it as the new master makes later revisions harder. Your master should preserve the work needed to produce another version. It does not have to be a particular format in every application, but it should not depend on the existence of a single web-sized attachment in a sent email.
Decide on dimensions before compression
Pixel dimensions describe how much image information an export contains across its width and height. A file can be large in storage without having the dimensions a destination needs, and a small file can look excellent when displayed at an appropriate size. Start with the actual display or print requirement. Avoid increasing dimensions simply because a bigger number feels safer.
For web use, consider the image's largest expected display and the destination's own guidance. A tiny thumbnail does not require the same export as a full-width photograph. Sending much larger files than needed can increase upload and download work without improving the displayed result. Sending files that are too small can force enlargement and reveal softness. A short test on the real page is more useful than arguing about an abstract ideal.
For print, use the lab's instructions to connect the intended physical size with the required pixels. The resolution field alone cannot create detail that the image does not contain. Changing a number in a metadata box is different from resampling the photograph. If the proposed print is much larger than previous work, ask the printer about a proof or inspect a representative crop before ordering the final piece.
Make the crop a deliberate choice
Different destinations have different aspect ratios. A horizontal photograph may need to fit a square card, and a familiar print size may not match the original frame. Choose the crop yourself when the composition matters. Otherwise an automated center crop may remove a face, cut a useful gesture, or leave a caption referring to something no longer visible.
Keep a little flexibility when exporting for someone else's layout. If the designer will place the image in several shapes, ask whether an uncropped file is more useful. A final crop and a flexible source serve different needs. Label them clearly rather than sending two similarly named files and hoping the recipient notices the difference. Include any composition constraints in the delivery note.
Review the corners and edges after cropping. A small adjustment can introduce an awkward fragment or remove context that made the original image understandable. Also consider how an image will sit next to text. A face looking out of the frame may work differently on a page from the way it worked in the editor. Destination-aware cropping is an editorial decision, not merely a geometric one.
Choose a format the recipient can use
A widely supported photographic format is often practical for everyday sharing, while a workflow that needs transparency, extensive editing, or particular print requirements may call for something else. Consult the destination's accepted formats. A technically sophisticated file is unhelpful if the recipient cannot open it or if the platform quietly converts it in a way you did not inspect.
Compression should be evaluated on the exported file, not only on the preview in the export dialog. Look at fine texture, gradients, high-contrast edges, and any lettering in the image. These areas can reveal artifacts before an ordinary glance at the whole picture does. Compare at the intended display size as well as a closer view. A setting that looks identical in normal use may save substantial storage.
Avoid a repeated cycle of exporting, editing the export, and exporting again. Return to the master for revisions. Keep one delivery folder per purpose or version, so a compressed social copy does not accidentally become the source for a print order. This is a simple organizational decision that protects quality more effectively than always choosing the largest possible file.
Handle color as a workflow
Color appearance depends on the file, application, display, viewing conditions, and any conversion performed by the destination. A photograph that looks different on two screens is not automatically evidence that the export failed. Start by using the destination's color guidance and the application's supported color-management workflow. Do not strip or change profiles casually in an attempt to make every display match.
For ordinary web delivery, a commonly supported color space is often the practical choice unless the platform instructs otherwise. For a specialist print workflow, the printer may have different requirements. Ask before converting files based on advice intended for another destination. Keep the master so a mistaken conversion can be corrected without trying to reconstruct lost editing flexibility from a delivery copy.
Review important color work on a reasonably consistent display in stable light. A screen set to an extreme brightness or a room lit by strongly colored lamps can distort judgment. This does not mean every casual photograph needs a professional proofing setup. It means that a persistent mismatch deserves a controlled comparison before you start moving color sliders to compensate for an unknown cause.
Check metadata before sending
Photographs can carry capture information, location details, names, captions, and other metadata. Decide which fields the recipient actually needs. A family archive may benefit from names and dates, while a public website may not need precise location information. The correct choice depends on consent, context, and the use of the image. Metadata removal should be deliberate rather than an automatic promise that all privacy concerns are solved.
The visible picture can reveal information that metadata controls cannot remove. A house number, shipping label, reflected screen, or recognizable routine may matter more than a location field. Inspect the image itself before public delivery. If sensitive material must be obscured, use an appropriate editing method and verify the exported result. Merely placing a reversible element in an editable project is not the same as delivering a safely flattened image.
Keep useful rights and credit information where the destination supports it. If the photograph belongs to someone else, export settings do not replace the license or permission requirements. A delivery note can clarify intended use and attribution. Preserve a record of the source and terms separately, because metadata may be stripped by platforms or lost during later handling.
Name the file for the handoff
A filename should help the next person identify the picture and its purpose. A short project name, a meaningful subject, and a version or sequence identifier are usually more useful than a string of emotional labels. Avoid calling several files final. If a correction is made, create a clearly distinguished revision and tell the recipient which earlier copy it replaces.
Do not embed private information in names when files will be publicly accessible. Names can appear in URLs, download dialogs, email previews, and search systems. A descriptive but restrained filename is often enough. Keep the fuller identification in the private archive when needed. This separates retrieval needs from unnecessary public disclosure without making the delivered files impossible to understand.
For a set, use consistent naming and a simple delivery list. Tell the recipient whether the files are intended for web, print, or further editing. If two sizes are included, put them in clearly named folders. The handoff should make the correct choice easy. A perfect export hidden among old drafts is still a poor delivery.
Inspect the result where it will live
Open the exported files in a normal viewing application. Confirm the crop, orientation, dimensions, and visible detail. Upload a test when the platform will transform the image, then inspect the displayed result on a larger screen and a phone. A local file can be correct while an automated crop or compression step changes the final appearance.
Keep the test focused. You do not need to compare every pixel of every photograph, but check representative images and any file with difficult gradients, small details, or important text. If a problem appears, change one export decision and repeat the comparison. This produces useful evidence instead of an endless sequence of increasingly large files with no clear improvement.
Once a configuration works for a regular destination, save a preset with a descriptive name and review it when the destination changes. A preset is a starting point, not a permanent guarantee. The reliable routine is to preserve the master, export for a known purpose, and examine what the viewer actually receives. That small final check is often where a technically correct file becomes a successful photograph in use.
Questions or a correction? Contact Tian Xin Kai at [email protected].
General educational guidance. Features vary; check your device documentation before changing settings.


