File Size, Resolution & Formats
In collectible photography, file size, resolution and format are not merely technical settings. They determine whether an image can reveal a printing distinction, survive enlargement, reproduce accurately in a catalogue, load efficiently on a website, preserve embedded evidence and remain usable years after it was created.
A photograph may look adequate on a phone yet fail when a collector needs to inspect a publisher's mark, compare paper texture, document restoration or prepare a full-page reproduction. The correct goal is therefore not one universally "best" file. It is a controlled family of files in which the source is preserved, a stable master is identifiable and smaller derivatives are created deliberately for particular forms of sharing and publication.
Central collector principle
Preserve the source, establish the master and publish purpose-built derivatives.
This protects three different values: what the photograph can demonstrate, what is known about its creation and subject, and how effectively it can be viewed or reproduced. Convenience copies should serve access without silently becoming the only surviving evidence file.
Three measurements that answer different questions
Resolution, file size and format are connected, but they are not interchangeable. Confusing them leads to weak publication specifications and false confidence in files that are large without being informative.
Resolution
How many pixels are available
Pixel dimensions describe the image's spatial capacity: 3,000 x 2,000 pixels, for example, contains six million pixels. They do not guarantee that the photograph is sharp, well lit or capable of resolving the feature under examination.
Collector risk
A large but blurred file can carry less usable evidence than a smaller, sharply focused close-up.
File size
How much storage the file occupies
Megabytes are influenced by pixel count, compression, bit depth, image complexity, metadata, colour profiles and editing layers. File size is an operational fact, not a direct quality score.
Collector risk
Treating the largest file as the best file can conceal severe blur, poor capture or inefficient encoding.
Format
How pixels and supporting information are packaged
JPEG, TIFF, PNG, WebP, AVIF, HEIC, raw and layered working files have different roles. Format choice affects compatibility, compression, metadata, bit depth, transparency and future usability.
Collector risk
No single format is simultaneously the ideal camera source, preservation master, web image and universal publication file.
Myth versus reality
Changing 72 PPI to 300 PPI does not create print detail
Online display is governed mainly by pixel width and height. A 1,600-pixel-wide JPEG contains the same pixels whether its metadata says 72 PPI or 300 PPI. For print, PPI describes how those pixels are distributed across a physical size. It becomes meaningful only in relation to the final reproduction size.
print width in inches = pixel width / required PPI
Effective print resolution is conditional
Three hundred PPI at final size is a useful high-detail target for books and catalogues, not a universal border between good and bad printing. The required effective resolution depends on the press, paper, screening method, subject, viewing distance and publisher's workflow. A large exhibition panel viewed from several metres away may need substantially fewer pixels per inch than a close-viewed page showing a tiny printer's code.
| Intended use | Working guide |
|---|---|
| High-detail book or catalogue reproduction | About 300 PPI at final size |
| General publication | Often 240-300 PPI |
| Large display viewed farther away | Often 150-240 PPI |
| Archival capture | Retain full useful native dimensions |
Worked example: a 6,000 x 4,000-pixel capture
300 PPI
20 x 13.3 in
240 PPI
25 x 16.7 in
200 PPI
30 x 20 in
150 PPI
40 x 26.7 in
These figures describe pixel allocation, not guaranteed visual quality. Blur, glare, excessive noise reduction and a subject occupying only a small part of the frame can reduce the useful print size long before the arithmetic limit is reached. Cropping also reduces the available dimensions.
Useful resolution is measured against the feature
A collector does not need abstract megapixels. The collector needs enough sharp, well-lit pixels on the feature that supports the judgement. A 4,000-pixel overview of a large poster may reveal less about a printer's mark than a 2,000-pixel close-up made specifically for that mark.
Evidence test
Can the image resolve the feature on which the judgement depends?
Test tiny printing codes, fibres, mould lines, repair boundaries, faint signatures, embossing, seal texture, corrosion pits and edge recolouring at 100% view. Headline megapixels do not answer this question.
Collector risk
Presentation enhancement is not evidence enhancement
Upscaling can make an image smoother or easier to inspect, but interpolation and AI may invent plausible texture, lettering or edge structure. Label the result as an enhanced derivative and retain the source from which it was made.
Cropping and downsampling are irreversible decisions
Reducing a 6,000 x 4,000 image to 1,500 x 1,000 removes fifteen-sixteenths of its pixels. Cropping a central 2,000 x 2,000 square from that same capture leaves a four-megapixel file. Both operations can be entirely appropriate for publication, but neither should silently replace the retained source.
Preserve context and detail separately
Overall view
Retain a full or conservative frame showing scale, edges, packaging, neighbouring features and the relationship of a defect to the whole object.
Dedicated detail view
Photograph the mark, defect or texture at an appropriate scale rather than depending on an extreme digital crop from the overview.
Compression changes what survives
Lossless compression reconstructs the currently encoded pixels exactly. Lossy compression permanently simplifies them. Neither term proves that the photograph is original, truthful or high resolution; it describes only what the encoding process does to the data it receives.
Lossless
PNG, suitable TIFF compression and some WebP, AVIF, raw and DNG options can reduce storage without changing decoded pixel values.
Best suited to
- masters and substantial editing workflows;
- graphics, text and line work;
- cases where another lossy generation would be undesirable.
Lossy
JPEG and lossy web encodings trade some data for much smaller files. At good settings this can be visually excellent; at aggressive settings it can erase precisely the detail a collector is trying to communicate.
Inspect for
- blocks, ringing and halos around type;
- smearing of fibres, scratches and halftone patterns;
- colour bleed around signatures and printed edges.
Repeated JPEG saving causes cumulative damage
Opening or viewing a JPEG does not normally degrade it. Damage occurs when it is decoded and saved again with lossy compression. Social-media downloads, screenshots, messaging apps and repeated crop-export cycles can create several generations of loss.
- Retain the camera source or master.
- Edit from that source or a non-lossy working file.
- Create a fresh derivative for each publication requirement.
- Do not use a small prior publication copy as the new working master.
Bit depth and colour are production controls
Higher bit depth provides more tonal precision during editing, particularly when recovering shadows, correcting exposure, adjusting white balance or describing subtle fading and gloss. Most ordinary JPEG delivery files are 8-bit per channel; raw and 16-bit TIFF working files preserve more editing latitude. The advantage is usually in the production process, not an automatically visible improvement in the final web image.
Web
Use intentional sRGB
sRGB is normally the safest colour space for websites, marketplaces, email and general interchange. Embed the profile where the workflow allows it.
Master
Retain managed colour
Wider-gamut and high-bit-depth masters can preserve difficult inks, textiles, paints and packaging colours for controlled later conversion.
Do not guess CMYK
The correct CMYK profile depends on press, ink, paper and regional workflow. Many publishers prefer profiled RGB and make the final conversion themselves.
Choose formats by role, not prestige
A format should be judged by what must survive and who must open it. The following cards describe defensible collector roles rather than a universal ranking.
Camera raw and DNG
Capture sourceStrengths
- Highest editing latitude and capture precision
- Strong source record for exposure, colour and later rendering
- Useful for important objects, condition surveys and publication work
Limitations
- Not a universally viewable finished photograph
- May depend on proprietary software or sidecar instructions
- A converted DNG is not automatically the untouched camera original
Collector use
Retain raw for significant captures and accompany it with an accessible rendered master. For conservative evidential work, keep both the proprietary raw and any DNG conversion.
TIFF
High-quality rendered masterStrengths
- Supports high bit depth and lossless workflows
- Mature in scanning, preservation and print production
- Suitable for subtle tonal, colour and surface evidence
Limitations
- Large files and unnecessary bandwidth for routine sharing
- The TIFF family permits configurations with uneven interoperability
- Layers or uncommon compression can complicate exchange
Collector use
Use for edited archival masters, high-resolution scans and publisher delivery when requested. Do not create TIFFs merely to make ordinary listing photographs look more professional.
JPEG
General exchange and photographic deliveryStrengths
- Near-universal compatibility
- Efficient for continuous-tone photographs
- Practical for collection systems, email, listings and catalogues
Limitations
- Lossy compression can obscure fibres, scratches, print texture and small type
- Repeated saving causes cumulative damage
- Quality numbers are not consistent between applications
Collector use
Usually the safest delivery format. Export a fresh, high-quality JPEG from a retained source or master rather than repeatedly editing a previously compressed copy.
PNG
Graphics, screenshots and transparencyStrengths
- Lossless storage of rendered pixels
- Excellent for text, line work, labels and hard edges
- Supports transparency
Limitations
- Photographic files are often much larger than JPEG or WebP
- Lossless does not mean original, unedited or evidentially trustworthy
- Application metadata handling can be inconsistent
Collector use
Use for diagrams, condition maps, screenshots, marks, logos and transparent cut-outs. It is rarely the most efficient format for a conventional object photograph.
WebP and AVIF
Modern responsive web derivativesStrengths
- Efficient delivery at multiple display sizes
- Can support lossy or lossless encoding and transparency
- Useful for thumbnails, cards and enlarged web views
Limitations
- Publisher and older software acceptance is less universal than JPEG or TIFF
- Encoding choices can soften fine evidence
- Metadata survival must be tested rather than assumed
Collector use
Excellent website derivatives when the platform controls fallbacks and source retention. They should not ordinarily be the sole surviving copy of an important photograph.
HEIF and HEIC
Modern phone sourceStrengths
- Efficient capture with possible high bit depth and computational data
- May retain depth, sequence or multiple-image information
- Often the closest available source record from a phone
Limitations
- Uneven compatibility across marketplaces and desktop workflows
- Automatic conversion can alter orientation, colour or metadata
- Recipients may be unable to open the file
Collector use
Retain the phone original when it matters, but export a controlled high-quality JPEG for general sharing unless the destination explicitly accepts HEIC.
Working, layered and vector files
PSD, PSB and application-native files can preserve masks, adjustment layers, text, selections and compositing history. They are valuable when re-editing or edit transparency matters, but they are poor universal delivery formats. Retain them alongside a flattened master and an accessible viewing derivative.
SVG is useful for arrows, measurement overlays, diagrams and condition maps, not as the camera photograph itself. Keeping vector annotations separate from the underlying image prevents labels and circles from becoming permanently baked into the only copy.
Metadata support is not metadata survival
JPEG, TIFF and other formats may carry EXIF, IPTC and XMP information, but exports, social networks, marketplaces and conversion services may remove or rewrite it. Important descriptive and administrative information should therefore exist both within suitable files and in an independent collection or digital-asset record.
EXIF
Camera, lens, exposure, capture time, orientation, software history and sometimes location or device information.
IPTC
Title, caption, creator, copyright, credit, source, keywords and rights fields intended to travel with the image.
XMP
Extensible descriptive, administrative, rights and editing information, including links between assets and workflow states.
Internal or archival master
- full capture metadata where appropriate;
- capture date, equipment and colour profile;
- rights, source and catalogue identifiers;
- links to the object record and editing history.
Public derivative
- remove GPS, private addresses and sensitive filenames;
- omit device identifiers and internal workflow notes;
- retain suitable creator, rights and credit information;
- do not rely on the platform to preserve any embedded field.
Boundary with rights and security
Metadata decisions sit at the boundary between photography, rights management and collection security. Removing GPS from a public derivative is prudent; deleting every trace of capture and authorship from the archival record is not. Preserve internal evidence while publishing only what is appropriate to disclose.
Platforms create copies you do not control
A marketplace or social platform may resize, recompress, sharpen, strip metadata, alter colour handling, crop previews and serve different derivatives to different devices. A downloaded listing image may therefore differ materially from the file the seller uploaded.
Collector scenario: preserving a significant online acquisition
A rare boxed item is advertised with photographs that appear to show a subtle seal pattern and edge repair. The listing images are useful evidence, but the marketplace has reduced them and removed their metadata. A defensible record separates three things rather than treating one screenshot as the photograph.
Listing context
Screenshot the page with description, price, date, seller and visible claims.
Platform images
Retain the best downloadable copies and record their source and download date.
Seller originals
For significant purchases, request first-generation files or new close-ups of the disputed features where proportionate.
Publication systems need a derivative ladder
Serving a 6,000-pixel original into a 400-pixel card wastes bandwidth, decoding memory and processing time. The solution is not to discard the large source. It is to generate sizes matched to the interface and let the browser or platform select an appropriate derivative.
1
Source
Original upload retained outside routine page delivery
2
Master
Stable edited reference or approved rendering
3
Large
Detailed inspection, often around 2,000-2,400 px
4
Standard
Normal page view, often around 1,200 px
5
Thumbnail
Search, lists and navigation, often 200-600 px
High-density screens may benefit from a source roughly twice the CSS display width, but supplying the largest file everywhere creates unnecessary costs. Responsive selection is preferable to a single oversized image. File-size limits should not become evidence limits: if a platform resizes uploads, it should distinguish the user's source from its display derivatives and state clearly when originals are not retained.
A practical action hierarchy
At capture
Retain the native file, full useful dimensions and original metadata. Make overall and detail photographs deliberately rather than planning to rescue every feature by cropping later.
During editing
Work non-destructively where possible, use sufficient bit depth for substantial tonal correction, preserve an embedded profile and record significant edits. Never overwrite the only source.
For the retained master
Keep raw plus a rendered master, a high-quality TIFF, or a carefully controlled high-quality JPEG when simplicity and storage are legitimate priorities.
For online sharing
Export an appropriately sized sRGB JPEG, WebP or AVIF derivative; inspect it at 100%; remove private metadata while retaining appropriate credit and rights information.
For print publication
Ask for final dimensions, effective PPI, accepted formats, RGB or CMYK policy, colour profile, file-size limits, crop and bleed requirements, sharpening instructions and caption format.
Ask for measurable publication specifications
The phrase "high resolution" is too vague to guide delivery. It may refer to pixel count, scanning PPI, final print potential, file size, sharpness or simply a file larger than a thumbnail. Replace it with requirements that can be checked.
Print request
Minimum 300 PPI at the intended reproduction size, with the accepted RGB or CMYK profile and file format stated.
Evidence request
Original camera file or first-generation export, no resizing or AI enlargement, capture metadata retained, plus dedicated close-ups of the relevant features.
Diagnostic checklist before release
Resolution and framing
- Does the file contain enough pixels for the intended screen or final printed size?
- Is the feature that matters actually sharp, or is the headline pixel count misleading?
- Has cropping removed scale, edge geometry, packaging or surrounding context?
- Would a dedicated close-up record the feature more reliably than enlarging an overview?
- Has the image been upscaled, interpolated or AI-enhanced?
Compression
- At 100% view, are letters, fibres, line art and small defects still clean?
- Could blocks, halos, smearing or colour bleed be mistaken for wear or printing features?
- Has the image passed through repeated JPEG saves, social networks or messaging apps?
- Was the derivative exported from the master rather than from another derivative?
Format and compatibility
- Can the intended recipient or platform open the file reliably?
- Does the chosen format preserve the required bit depth, transparency and colour profile?
- Is the file a source, master, working file or delivery derivative?
- Has conversion changed orientation, colour, metadata, timestamps or embedded previews?
Metadata, colour and privacy
- Is descriptive and rights information stored outside the file as well as embedded where appropriate?
- Has private GPS, address, device or workflow information been removed from the public copy?
- Is an ICC profile embedded and has general web output been intentionally converted to sRGB?
- Does the publisher want RGB, or a specific CMYK conversion prepared for its press and paper?
Evidence and continuity
- Is the original capture retained?
- Can the published copy be traced back to its source and recorded edits?
- Are AI enhancement, interpolation, compositing or significant retouching clearly labelled?
- Are important masters backed up and, where proportionate, protected by checksums?
Common myths and the collector reality
Myth
The larger file must be better
Reality
It may simply be less efficiently compressed, layered or full of redundant data. Sharpness and useful evidence matter more.
Myth
PNG is always better because it is lossless
Reality
PNG is excellent for graphics but often wasteful for photographs. A carefully encoded JPEG may be visually excellent and far more practical.
Myth
Raw proves the image is authentic
Reality
Raw can strengthen the capture record, but authenticity still depends on custody, context, content and the history of the file.
Myth
Converting a JPEG to TIFF restores quality
Reality
It can prevent another lossy save, but it cannot recreate detail that JPEG compression already removed.
Myth
Metadata stays attached when an image is shared
Reality
Many applications and platforms strip or rewrite it. Store essential information independently from the image file.
Myth
WebP or AVIF should replace every other format
Reality
They are strong delivery formats. Preservation, professional exchange and long-term access still require source retention and compatibility planning.
What file characteristics can and cannot prove
Evidence
They can support
The identity of a specific file version, native dimensions, embedded capture information, a documented conversion and whether a checksum has changed.
Meaning
They do not establish
That the depicted object is authentic, the photographer owned it, the timestamp is accurate, the content was truthful or editing did not occur before the record was preserved.
Collector risk
Do not overclaim
Raw, TIFF, a large file, intact EXIF and an old creation date may strengthen a chain of evidence. None proves authenticity in isolation.
Checksums verify file identity, not visual truth
A cryptographic hash can show whether a file has changed since the hash was calculated. It cannot show whether the image was edited beforehand, whether the timestamp is correct or whether the object is genuine. Its value lies in managing exact file integrity, archival copies and the relationship between masters and published derivatives.
Specialist thresholds
Routine collection records can usually be handled with a disciplined camera-to- derivative workflow. Seek a professional photographer, reprographer, imaging specialist, conservator or prepress operator when the photograph itself becomes a high-stakes measurement or publication asset.
- Colour must support attribution, fading analysis or variant research.
- The image will appear in a major book, catalogue or exhibition publication.
- Reflective, transparent, iridescent or fluorescent material must be reproduced accurately.
- Ultraviolet, infrared, raking-light or microscopic imaging is proposed.
- Tiny printing characteristics or signatures are being compared.
- The image may become legal, insurance, conservation or authentication evidence.
- The object is too large, fragile or valuable for routine handling.
- Archival scanning, controlled targets or publisher-specific CMYK preparation is required.
Key takeaways
- Pixel dimensions, file size and format answer different questions.
- Useful resolution depends on sharp pixels across the feature that matters.
- Changing PPI metadata does not create captured detail.
- Keep the source and generate derivatives rather than replacing it with a smaller copy.
- JPEG is often the best exchange format, not necessarily the best source or master.
- Metadata, colour profiles and orientation must be tested through the actual workflow.
- Modern web formats improve delivery but do not remove the need for preservation masters.
- File characteristics can support a chain of evidence but cannot prove authenticity alone.
Continue learning
Editing Without Misleading
Understand when tonal correction, cropping, cleaning and enhancement cross from clarification into distortion.
Back to Sharing & Publication
Return to the complete section on selecting, preparing, describing and distributing collectible photographs.
Rights, Privacy & Attribution
Continue to ownership, credit, permissions, sensitive information and responsible photographic publication.
Related topics
Captions, Context & Metadata
Connect file handling with the descriptive, administrative and rights information that makes an image intelligible later.
Choosing Images for Purpose
Decide which views, details and image sets are appropriate for research, listings, insurance and publication.
Linking Images to Catalogue Records
Ensure source files, masters and derivatives remain attached to the correct object and catalogue identity.
Originals, Edits & Derivatives
Develop a controlled version structure so a convenient web copy is never mistaken for the source photograph.