Image tool guides

Every tool used to POST your photo to a Django server and store it on Cloudinary. Now none of them do. Here is what changed, what it cost, and what it bought.

Upload forms rarely say what went wrong. There are only five likely causes, and they are quick to work through in order.

A 4K screen shows 8 megapixels. A quality 10x8 print needs 7. Most photos are several times larger than anything will ever display.

The file is fine. The software you are opening it in was written before WebP existed and nobody updated it.

Dimensions first, format second, compression third, loading strategy fourth. Getting the order wrong wastes most of the benefit.

Two photos can look equally blurry and have completely different prospects. What matters is whether the detail is dim or absent.

Most panorama failures happen at capture, not at stitch time. Five minutes of shooting discipline fixes almost all of them.

Four distinct kinds of damage, four different causes. Identifying which one you have tells you whether it can be fixed.

The number is not a percentage and it is not comparable between tools. Here is what it does and where to put it.

You cannot tell what a QR code does by looking at it. That is the entire basis of the scam, and the fix is to read it as text first.

The camera is the easy part. Getting flat lighting and a square angle is what separates a scan from a snapshot.

It is the combination of a lossless format and a very high pixel count. Both are fixable, and one of them matters far more.

A photo straight off a phone can pin the exact spot it was taken. Re-encoding is the simplest way to remove that.

Every platform downscales and re-encodes what you upload. Matching their target dimensions first is the only way to keep control.

A 1000x800 image is 1000x800 whether its metadata says 72 or 300. DPI only becomes real when something physical is printed.

Quality settings get you most of the way. When they do not, the problem is resolution, and no amount of compression fixes it.

Shrinking a photo throws away most of its pixels. Which ones you throw away decides whether the result looks sharp or shimmery.

Lossless gives back every pixel exactly. Lossy gives back something that looks the same. The difference decides your format.

WebP wins on size by a consistent margin. JPG wins on everything outside a browser. Pick by destination, not by benchmark.

ELA and a few eyeball checks. Won't catch every fake, but catches the lazy ones.

When the QR code is on the same screen as you, pointing your camera at it doesn't work. Here's the alternative.

Smaller JPG files at the same visual quality. Here's the simple rule, the right quality number, and the common mistakes to avoid.

iPhone photos are routinely 3-5 MB. Here's the no-app way to shrink them.

Three formats cover 99% of the web. Here's a quick rule for picking one, plus the file-size numbers that prove it.

Hero photo to brand palette in 30 seconds. Hex codes ready to paste.

Gmail caps at 25 MB. Most corporate inboxes cap at 10. Here's the fastest fix.

The simple rule with proof. Then the edge cases where the rule flips.

Downscaling is mostly safe. Upscaling needs care. Here's a one-page guide that covers every common case.

Get a clean cutout in three clicks. Free, no signup, no watermark on the download.

Lossy throws away pixels you won't miss. Lossless keeps everything but compresses redundancy. Here's the rest.