You shouldn't assume. I didn't say that OP should use those JPG or TIFF images as their archive. It's not what I do and it's not what I said.
I said export so OP could easily use finished images in their thumbnails and other use cases that they mentioned, even though they might be shooting in other formats, and creating layered images with type, etc.
Aaah, my bad. Apologies: within the context of the entire conversation it seemed to me as if you were suggesting not to save your final work in a source native file format. It is sometimes difficult to understand the intent of a post with all the noise.
Is there a lossless format(s) that are good to use for archiving?
Is there a file format that preserves most, if not all, of one's work, but would open/work in other photo-editors?
While proprietary, file formats like .XLS and .DOC are widely supported among office productivity tools.
Likewise, .WAV and FLAC are pretty universal.
It is of some interest that no one perfect interchange file format exists for images. Each file format has its own limitations depending on the context in which it is used.
The ideal bitmap format would have to support:
- (as good as) limitless pixel dimensions and file sizes
- 1bit, 8bit, 16bit, 32bit depth per channel
- RGB, CMYK, LAB, HSV/HIS, YCbCr, and other (custom?) image modes
- 1bit, 8bit, 16bit, 32bit transparency
- HDR (High Dynamic Range)
- an arbitrary number of alpha channels
- an arbitrary number of custom channels
- animation frames
- both lossless and lossy compression algorithms
- colour (chrome) subsampling control
- masks/selections
- pages/tiles of bitmaps
- storage of multi-resolution images (mipmaps or ripmaps)
- layers
- encoding and decoding speed control
- meta data support for both common as well as custom fields
- storing of additional supporting data
- colour management
- browser displayable
Regular Tiff only saves up to 4GB large files, for example. Also a potential issue with tiff: Adobe decided to add their own proprietary Photoshop data stream, which means a tiff saved from Photoshop may include layers, which often cannot be read by other software. Incompatible with browsers and the web. No animation support.
But it does support 1bit up to 32bit depth per channel. And CMYK/RGB. Multiple pages. Both lossy and non-lossy compression. Colour management. Vector clipping mask.
JPG is quite restricted, uses an outdated compression method, and is not a great lossy-only 8bit-only bitmap format, unless we are stuck in older workflows and web standards. WebP and AVIF as a JPG replacement are a much better choice: lossless and lossy, transparency, better compression vs quality (in particular lossy AVIF vs JPG), animation support, 16 bit per channel.
But neither WebP or AVIF support CMYK. Bummer. JPG does.
Another example: PNG. Non-lossy, 1 to 16bit depth, full transparency, animation support. But no lossles support, and, while great for low-colour art, compression of full colour artwork or photos is less than stellar. And it lacks CMYK support.
PSD sounds like an excellent alternative: it pretty much supports all of the above. But it is a proprietary file format, and isn't documented very well - Adobe made certain of that (at some point their PSD file format spec was no longer updated to prevent the competition from having full compatibility with Photoshop's native file format). And Photoshop sets a paltry 30,000 pixel limit to width and height for its PSD files and a max 2GB. Even PSB files saved from Photoshop only scale up to 300,000 px in width and height.
Which doesn't seem to be a theoretical limit (and only one that Photoshop enforces on the user), because I can save PSD/PSB files from PhotoLine that easily exceed those limits. While PhotoLine will open these files, Photoshop absolutely refuses ;-P
Most of the common kitchen sink bitmap file formats can't practically (and technically) handle more than 16K or at most 65K in width and height. Compressing such large files using a lossy format tends to be super slow anyway.
A file format used in the 3D and visual effects industry comes close:
OpenEXR is an open non-proprietary spec bitmap file format, and has (almost no) theoretical limits to file resolution. It works with multiple (render) layers, allows for masks to be embedded, is by default 16bit or 32bit depth, lossless and lossy compression methods, alpha channels, and so on.
Well supported in software as well. But no animation support, and not suitable for lower-spec common bitmap tasks, such as average 8bit photos and images. Basically: EXR is complete overkill for most users. And doesn't play well in lower-end contexts nor are displayable in web browsers!
Anyway, it depends on the context, content, and user(s) which bitmap file format will work best for which particular job. No simple answers here.
@Ambrosia7177 Confused yet? Most people are and stick to older formats such as JPEG and PNG. Many still even use GIF these days. Which is a crying shame, because it wastes a lot of bandwidth and energy online. Various JPEG replacements have been doing the rounds, some met some success, others failed. JPEG XL would be a grand replacement. Let's hope it succeeds. WebP and AVIF are generally a better choice than either PNG or JPEG on the current web.
Adobe Photoshop is one of the main factors to blame behind the slow adoption of newer web formats. Photoshop's support for these is ABYSMAL and (in my opinion) an UTTER DISGRACE. The so-called 'new' Export As dialog doesn't even support WebP yet. After a decade of users pleading for it, only Save As supports saving WebP images. [facepalm]
AVIF can't even be saved from Photoshop. Those &$#@ developers even REVERSED full 8bit transparency support for indexed PNG images a few years ago!!! Only 1bit transparency is now possible!!! Seriously frustrating, and it wreaked havoc with the workflow of many screen and web designers.
Check out image file support of various image editors here:
en.wikipedia.org
My primary use will be to edit (and optimize) photos that I take with my iPhones (and future mirrorless camera) for my mobile website.
But creating professional-looking YouTube thumbnails is a close #2.
Use AVIF for all your web exports on the mobile website. Much smaller file sizes at a higher quality and higher resolution. Faster download and display speeds for your average mobile user. WebP is also an option, but AVIF is just superior on all counts for web photographic images right now.
caniuse.com
Avoid JPG(JPEG) in my opinion. Terrible outdated format compared. (I realize I might be poking a Hornest's nest with this comment ;P)
Problem is: Only a few image editors support AVIF export. Yet 95% of the world's currently used browsers read and display AVIF without issues.
More interesting topics: It can be interesting to see the Library of Congress's approach to archival formats since that's what they do for their day job. TIFFs and JPEGs are there, and PSDs are reasonable approaches.
For what they think, here's a good link:
https://www.loc.gov/preservation/digital/formats/fdd/still_fdd.shtml
@r.harris1 Thanks for that link! Useful, even if those archivists are also somewhat behind the times. Well, they're supposed to be conservative (pun intended) in their approach
