A photo can look fine in an editor and softer in a message or shared album. Before editing it again, find out whether the saved file changed or the destination is showing a different preview. Keep your accepted edit untouched while you check.

Keep three checkpoints separate

Use the same selected version throughout:

  1. Saved edit: the actual file you chose to share, opened outside the editing screen.
  2. Received file: the attachment or download obtained from the destination, when available.
  3. Destination preview: the image displayed in the message, album or webpage.

If the destination does not let you obtain the received file, you cannot tell from its preview alone whether the file itself lost detail. Record that checkpoint as unverified.

A screenshot of a preview is another image. It cannot substitute for the file you meant to send. Do not compare the unedited input with an edited result when investigating transfer quality: the edit itself may legitimately change detail.

Compare under the same viewing conditions

Open the saved and received files in the same viewer on the same device. Use the same window and comparable display size. First inspect the whole composition, then look closely at the same small features. Note the zoom rather than comparing an enlarged view with a small thumbnail.

Cabin among pine trees, with a straight roof edge, porch rails and gravel in the foreground.
Input from an earlier Lumia promotional example. Use the roof, rails and branches as comparison landmarks. This is not a current export or a sharing-quality test.

In the cabin example, useful landmarks are the roof edge, porch rails and pine branches. Follow those same landmarks through copies of one chosen version. The picture illustrates where to look; it does not demonstrate a Lumia sharing defect.

Check pixels and compression separately

Record each file’s width and height in pixels, format and file size. A change in pixel dimensions is direct evidence that you are comparing different-sized images. Confirm that neither copy has also been cropped or rotated.

For example, a hypothetical 543 × 724 copy of the 1086 × 1448 cabin input has half as many pixels on each axis and one quarter of the total pixels. No such transferred copy was tested here. Enlarging that smaller copy on screen does not recreate the discarded detail.

Equal dimensions do not prove equal image data. JPEG compression can discard information and soften fine edges even without a change in width or height. Adobe explains this trade-off. File size alone is not a quality score.

Choose the next step from the comparison

  • The saved edit already looks soft: investigate the input, edit and save/export stage first. A different sharing route cannot fix detail missing from that file.
  • The saved edit is acceptable, but the received file is worse: check the particular sending, resizing or download step. Consult that destination’s current instructions and compare a new transfer from the retained file.
  • The received file looks acceptable, but its preview looks soft: investigate the destination’s preview or display. More editing may be unnecessary.
  • The crop, version or framing differs: find the matching files before drawing a conclusion about quality.

A sharing service’s preview and downloadable image need not be equivalent. An Adobe support discussion illustrates that distinction for Lightroom; it does not establish how every service works.

Keep a useful comparison record

If you need help, note the app and operating-system versions, chosen save/share route, destination, both files’ dimensions and which checkpoint first looks different. Describe one visible feature, such as “the porch rails merge together only in the received copy.” Use an appropriate non-private example if you choose to share one.

Lumia’s current listing describes creative photo editing. This checklist has not tested its current export settings, compression or any messaging service. It helps you narrow down the step to investigate before repeating the edit.