A folder contains different roles

A photography demonstration can leave several files that belong to one image but serve different purposes. The captured file, an exported image and a metadata sidecar are not interchangeable. Adobe's Camera Raw and Lightroom documentation explains how settings and metadata can be stored in external sidecar files alongside native images. At an expo workshop, begin by identifying each file's role rather than judging only by filename similarity or size. A folder may contain the captured data, instructions for interpreting edits and a rendered version intended for sharing. Reading those relationships explains why several files can be part of one workflow without being duplicate photographs.

The captured file is a source object

A file identified as the original capture supplies the starting object for the demonstrated workflow. Its format and provenance should come from the camera or workshop explanation. The word original can describe that role without guaranteeing that a later folder contains the untouched first file. A renamed copy can retain the captured data while changing its filename. A converted file may have a different relationship to the source. At a workshop, record what the presenter means by the label. This keeps provenance and file format separate: the extension describes a type, while the documented sequence explains how that particular object entered the folder.

An export is a rendered output

An export can apply the workflow's settings and produce a file in the chosen output format and dimensions. It is a result of the process rather than simply another name for the capture. Two exports from the same source can differ because their settings or purposes differ. A small web version and a larger print-oriented version can therefore share an image without being identical files. Read the exported file's dimensions and stated purpose. The workshop's comparison becomes clearer when those fields remain visible. File size alone cannot explain which settings were applied or whether the export is the output the demonstration intended to illustrate.

Metadata describes rather than depicts

Metadata can identify characteristics, settings or descriptive information associated with an image. Adobe documents external XMP sidecar files as one place for such information, with storage behavior depending on the workflow and file type. A sidecar is not a second visual image merely because it sits beside one. Its relationship to the image is the important fact. At a demo, read the filename association and the software's explanation of what is stored. The audience can understand the concept without opening every technical field: one object supplies image data, while another can supply information used to describe or interpret that object within the workflow.

Trace a fictional three-file set

Imagine a hypothetical folder containing PhotoL.raw, PhotoL.xmp and PhotoL-web.jpg. These illustrative names do not identify a real camera format or workshop download. The first represents the source capture in this workflow. The second represents associated settings or metadata. The third represents a rendered web export. Deleting the distinction and calling all three “copies” would misdescribe their roles. Now add PhotoL-print.jpg with different stated dimensions. The folder contains two outputs from one source, alongside supporting information. This example shows how filenames can help organize relationships, while the workshop's documented sequence establishes what each object actually represents.

Extensions identify types, not complete histories

A familiar extension can suggest a file format, but it does not prove the full sequence that produced the file. A JPEG might be a camera capture, an export or a later edited copy. The actual provenance requires the workflow record. Similarly, two files with different names can contain the same image data, while two similarly named files can represent different states. At an expo workshop, keep a short sequence note: captured, settings applied, export produced. That note adds information the extensions cannot supply. The goal is to understand the demonstrated relationship rather than infer an entire history from a few characters after the filename.

Dimensions and size measure different things

Pixel dimensions describe the image's raster extent. File size describes stored data volume. They are related through format and content, but they are not the same measurement. A 2,000-by-1,500-pixel image contains three million pixel positions, while its file size depends on how the file stores them and other information. A larger file is not automatically a larger picture in pixel dimensions. Record both measures with their units when the workshop uses them in a comparison. This makes the folder's outputs easier to interpret and prevents a storage number from being treated as a complete statement about image dimensions or provenance.

Preserve the workflow's relationships

A useful record identifies the source, associated settings or metadata, and each export's purpose. It can be brief: “One captured file, one associated sidecar and two rendered outputs.” Add the actual names and dimensions when the demonstration supplies them. At a photography workshop, this structure turns a confusing folder into an understandable sequence. The reader can distinguish data, descriptive information and rendered results without treating them as interchangeable duplicates. It also supports a more precise conversation about what the presenter has delivered: a source object, an output or the supporting information that connects stages of the demonstrated workflow.

Continue exploring

Explore related events

Current facts come from the directory. Follow the exact listing for admission, venue information and the official source.

STEMCON Public STEM Expo 2027 · Apr 24, 2027 · scheduled · Public visitor information — check organizer updates

Sources and further reading

Source review: 2026-10-12. Examples identified as hypothetical are original illustrations.

An independently researched feature. Worked examples are illustrative; photographs identify their archive or collection context.

Find your next event →