Pixel number and public viewing on a screen, not printed.By “reducing size,” do you mean physical size (number of pixels) or file size? And do you mean public viewing of a digital image on a screen, or a printed version?
I want to share a photo at its best but without giving away the full photo to anyone if I choose not .
What program are you using to export and what file type (jpg or png)? When exporting do you have your ICC profile saved/embedded to the file? I believe sRGB is still the standard for web viewing. Granted some browsers may have a larger color space and some of your audience may have a larger color space monitor but generally I still believe the safe bet is sRGBWhat is the best way to export a photo for public viewing without losing quality , just reducing size?
Quite often the photos I export are dull compared to the ones on my computer.
I'm going to disagree with the sentiment that placing a tastefully done watermark distracts from the image at all. Good composition is seen whether there's a watermark or not. I am also going to disagree that registering is the strongest legal recourse. Maybe semantics but the absolute best legal recourse due to some rulings is that a registered image (with the © office) And a watermark gives the strongest legal recourse. Plus if you show they removed the watermark © symbol don't you have an even larger legal recoup?And of course you can throw watermarks all over it, which may prevent someone from wanting to steal it, though it leaves you with an image that isn't as nice looking as your original.
For real protection, all you can do is register your images with the copyright office. It leaves you with your strongest legal recourse if you find someone has infringed on your work.
Googling gives me almost all about Lightroom, but thanks anywayi would just google “best export settings for xyz program.” 🙂 offsite hosting foyer results in better images if you have a host. if not, don’t sweat it.
Thanks for such a detailed answer and good tips!Reducing the resolution of any bitmap image will always result in a lesser quality image. It is as simple as that: removing pixels removes details from an image. This is reality.
That said, there are a couple of guidelines that work in any image editor to maintain an acceptable quality as long as the reduction in resolution is not too extreme (scaling down ten times is going to affect the image details, no matter what of course).
Generic step-by-step guide:
Saving your work may have a dramatic negative impact on image quality. JPG absolutely destroys sharp edged artwork or details at any setting lower than 90~92, because it is a lossy format. PNG is non-lossy and retain the exact pixel information, albeit at a much increased file size.
- before scaling down an image, sharpen it. Perhaps even overdo the sharpening: when it is scaled down to a much lower resolution version, this will at least visually preserve some details a bit better.
Be careful though: it depends on the type of image whether this pre-sharpening step will have a negative or positive impact. For example, I noticed a reduction in anti-aliasing quality along the edges for sharp-edged hand drawn illustrations. Photos generally do benefit from this first step. Test, test, test. It depends on the content and intent of each image.- scale down. The selected resampling algorithm may have an impact on preserving visual detail. For example, MitchellNetravali or CatmulRom are two of the better down-sampling algorithms, maintaining contrast around details better than for example bicubic.
Most image editors do not support these, however. PhotoLine is the only mainstream image editor that supports both as well as cubic spline and lanczos; Krita supports Mitchell too. A reasonable alternative is Lanczos, which is also supported by Affinity Photo.
Read up on this topic here:
Resampling Filters -- IM v6 Examples
legacy.imagemagick.org- after scaling down you may want to sharpen the image slightly (or a lot) depending on the content once more.
The sharpening algorithm may also have an impact on overall image quality, btw.
Again: test.- repeat steps with the same image using different sharpening and downsampling settings. Compare, and pick the one you like most.
- if content of the image differs greatly, repeat steps 1-4 once more to figure out the best settings.
Depending on the content (again) and the number of colours used, indexed or reduced colour palette export to PNG may be a solution. Or test webp at a higher quality, which tends to favour quality in smaller resolution images much better than jpg is able to achieve at smaller file sizes.
Unfortunately Affinity Photo still does not export to webp (which is just ridiculous in my opinion). So you would have to rely on other tools to do so.
The other thing that can be really useful is a real-time side-by-side web export preview. Unfortunately (again) Affinity Photo does feature such a preview option (which again is ridiculous in my opinion). PhotoLine, Photoshop, and other image editors do allow for this, and I tend to zoom in 200% while changing the export settings to check what the final quality would be.
This final step is not possible in Affinity Photo, however - and it kinda essential to have if we are interested in comparing quality with export settings. It is more trial and error in Affinity, and just takes too much time and effort.
Finally, you mention "dull" looking images. This may be due to colour shifiting caused by a broken colour management workflow. Check the original with the exported version and if there is a clear colour shift, you may have to test your colour management workflow.
A quick fix would be to use the Vibrance and curves adjustments in Affinity Photo to create a better looking version after exporting. Not the best way to go about it, though.
I am also going to disagree that registering is the strongest legal recourse. Maybe semantics but the absolute best legal recourse due to some rulings is that a registered image (with the © office) And a watermark gives the strongest legal recourse. Plus if you show they removed the watermark © symbol don't you have an even larger legal recoup?
Thanks for such a detailed answer and good tips!
I tried with several apps but so far Raw Power is giving me the best results , even if it works better from the app itself but not from the exporting extension in Photos. Not enough settings available , including the DPI
I agree that Affinity Photo should consider the web exporting
It changes if it's shown that the infringement purposely removed the symbol - that was my only point. I never said that the symbol supersedes registering the image(s) in the first place. I said in 'conjunction' with it being registered. There are recent rulings stating this very thought that without any type of warnings/watermark the photographer must not of been interested in protecting - as you stated.Sorry, but this is completely, legally unfactual.
Here's the reality. Under U.S. law, the act of creating an image by pressing the shutter button on a camera is a legal act as well as a creative one. Press the button and you have created a copyrighted work. Adding a © symbol changes nothing legally, aside from telling everyone that the work is copyrighted. Which it is already.
The protection afforded through copyright registration is purely one of legal recourse. As there is no legal defense for using an infringed work that the creator has taken the steps to protect, the claims against such use are much higher. So if someone uses a work that a photographer has registered, the claims - per infringement - can go from $30,000 to $150,000.
By not registering, it is easier to make a claim that the photographer was not interested in protecting their works. The courts have stated such, time and again. Often the cases are stopped with a complete settlement in the photographer's favor, once the infringer has been notified that the work was registered.
That is why I mentioned it is entirely context dependent. Even the art style and type of downsampling algorithm will have an impact. Often barely discernible, yet sometimes the final result suffers from horrible anti-aliasing along sharp edged artwork.I do question if Herbert's advice on sharpening prior to reduction is best practice for photos vs for graphics with hard lines verses sharping after the reduction has taken place.
Yes I have, and at my job I am of necessity well schooled in copyright. Have been for years. And at work we have attorneys whose bread and butter is copyright, and (thankfully) they are always there to answer questions, too.Curious have you ever actually been in involved in an actual copyright court case? I have and even if you win you never win going to court. Your black and white numbers and clear cut assumptions never happen in the real world until months of back and forth pain. If I can put a bit of effort to prevent then I'm good with that.
Something to realize about watermarks, too, is that they can be removed fairly easily by someone who is determined and who knows how to skillfully do it.
I don't have Lightroom but I could try to compare and use some of the settings elsewhere.
I already gave up to watermarks for the same reasons mentioned in this thread. I use Affinity Photos, RawPower and Photos to export. Anyone using those?
I was missing Affinity Photos, just found the other two. 😍
That generalized statement is so wrong on so many levels it is hard to know where to begin tearing it down.
- JPEG is usually best for images on the web
Again a statement without any clue as to how images in responsive web layout code work. This is WAAAY too vague and not based on good practices on dealing with web imagery.Keep sizes reasonable, there are many online guides but I tend to find around 1700px is a good compromise
One more vague and incorrect statement.
- Choose the highest quality that any file size restrictions will allow, anything about 80% is great