app.pixelmob.co

You can cut most images to a fraction of their original file size without any visible quality loss by doing three things in the right order: resize the image to the dimensions it will actually display at, pick the right format for the content, then apply compression at a quality level that survives a side-by-side check. The single biggest mistake is skipping step one — an oversized image compressed at maximum quality is still far heavier than a correctly sized one.

Why file size and quality are a trade-off, not a fixed setting

Every compressed image is a negotiation between three variables: how many pixels you keep, how precisely each pixel is described, and how much the format is allowed to guess.

• Dimensions decide how many pixels exist at all. Halving width and height removes 75% of the pixel data before any compression happens.
• Quality level decides how aggressively the encoder discards detail it thinks you won't notice.
• Format decides the kind of discarding allowed — some formats throw away color precision, others only remove redundancy.

Because these interact, "quality 80" means something different on a 4000px photo than on a 600px thumbnail. Tune dimensions first, then quality.

Pick the format before you touch the quality slider

Practical rule: photos → JPEG or lossy WEBP; flat graphics and transparency → PNG or lossless WEBP; anything vector → SVG.

The four levers, in the order you should pull them

1. Resize to display size (biggest win, zero quality cost)

If your layout renders an image at 800px wide, serving a 2400px original wastes roughly 89% of the pixels. Resize to the largest size it will ever be displayed at, and add a 2× version only if you need retina sharpness.

2. Choose the format

Match the format to the content type using the table above. Converting a photographic PNG to JPEG or WEBP alone can shrink it by 80% or more.

3. Set the quality level

For JPEG and lossy WEBP, most photographs hold up well between quality 70 and 85. Below ~60, banding appears in skies and blur around text. Above ~90, file size climbs steeply for gains nobody can see.

4. Strip metadata

EXIF data, camera info, and embedded thumbnails can add tens of kilobytes. Remove them unless you specifically need copyright or orientation data — and note that stripping orientation can rotate an image, so verify after export.

When lossy compression is fine, and when it isn't

Lossy is acceptable when:

• The image is a photograph or has natural texture.
• It's decorative or below the fold.
• Slight softening won't be noticed at final display size.

Use lossless or vector instead when:

• The image contains text, UI elements, or thin lines (lossy creates ringing artifacts).
• It's a logo, icon, or diagram — SVG or PNG keeps edges clean.
• It will be edited again later; repeated lossy saves compound degradation.
• It's a screenshot of code or a chart where color accuracy matters.

Compressing vs. resizing: don't confuse them

Compressing reduces the bytes needed to describe the same pixels. Resizing reduces the number of pixels. They're independent, and resizing usually delivers the larger saving. A 3000×2000 photo at quality 95 might be 2 MB; the same photo resized to 1200×800 at quality 80 might be 180 KB. Doing only the quality reduction gets you maybe 40% off; doing both gets you over 90%.

A repeatable workflow

1. Determine the maximum display width in your layout (inspect the element or check your CSS).
2. Export at that width (plus a 2× variant if needed).
3. Convert to the right format — WEBP as a modern default, JPEG as a fallback, PNG/SVG for graphics.
4. Apply quality 75–85 for lossy formats and compare against the original.
5. Strip metadata and re-check orientation.
6. Verify before publishing (see below).
7. Serve the right file with srcset so small screens don't download the large variant.

How to verify quality before you publish

• View at 100% at final display size, not zoomed in — artifacts you can't see at real size don't matter.
• Toggle between original and compressed in a viewer or an online compressor's before/after preview.
• Check the worst-case areas: skies, smooth gradients, sharp edges, and any text.
• Compare file sizes and ask whether the extra kilobytes buy visible improvement. If not, go smaller.
• Test on a mid-range phone, where banding and blur are often more obvious than on a desktop monitor.

Common mistakes

• Compressing a full-resolution image and calling it optimized.
• Using PNG for photographs.
• Setting quality to 100 "to be safe" — it inflates size with no visible benefit.
• Re-saving a JPEG repeatedly, stacking artifacts each time.
• Forgetting that GIF animations are usually better as WEBP or video.
• Ignoring metadata, which can silently add weight.

Quick reference

The order matters more than any single setting: resize, then choose format, then tune quality, then strip metadata, then verify at real display size. Follow that sequence and you'll routinely land at 10–20% of the original file size with no quality your visitors can detect.

Royalty-free stock photos are images you pay for once (or download free) and then use multiple times without paying per use or per impression. The "royalty-free" label describes the payment structure, not the copyright: the photographer or agency still owns the image, and your right to use it comes from a license. Before you publish, confirm three things in that license — commercial use, attribution requirements, and modification limits. If any of those are unclear, treat the image as unusable until you verify it.

Royalty-free vs. rights-managed vs. public domain

These three terms get mixed up constantly, and the difference determines what you can legally do with a photo.

The practical takeaway: royalty-free is the most flexible and affordable for websites, blogs, and social media, but it is never exclusive unless the license explicitly says so. If you need an image that competitors cannot also use, that is a rights-managed or custom-commission conversation, not a royalty-free one.

Public domain is not the same as royalty-free. A public domain image has no copyright owner (or the copyright expired); a royalty-free image is still copyrighted and licensed to you. Do not assume an image is public domain just because it is old or widely shared.

What common license terms actually mean

Most royalty-free licenses are built from the same handful of clauses. Read them as a checklist.

• Commercial use. Many licenses permit use in advertising, products, and client work; some free licenses restrict commercial use or require a paid tier. Confirm this before using an image in anything that earns money.
• Attribution. Some licenses require a credit line ("Photo by X via Y"). Others do not. If attribution is required, the exact wording and placement usually matter.
• Modification. Cropping and resizing are almost always allowed. Substantial edits, using a person's image in a way that implies endorsement, or incorporating the photo into a logo or trademark are commonly restricted.
• Sensitive-use restrictions. Licenses frequently prohibit using identifiable people in connection with controversial, political, or medical content. This applies even when the photo itself is neutral.
• Model and property releases. A license from a stock site does not automatically include a release from the person or property in the photo. For commercial or promotional use, check whether a release exists.

If a license summary on a site conflicts with the full legal text, the full text governs.

Where to find royalty-free stock photos

Sources fall into two broad groups: agencies that license their own catalogs, and aggregators that search across multiple sources. Pixel Mob (app.pixelmob.co) is an example of the aggregator approach — it describes itself as finding royalty-free stock photos from multiple sources for use on websites, blogs, and social media.

Aggregators are useful for discovery, but they add a step: the license that applies is the one from the original source, not the aggregator's summary. When you find an image through an aggregator, follow the link back to the source and read that license.

For any source, apply the same test:

1. Find the license page linked from the image or download button.
2. Check commercial use, attribution, and modification clauses.
3. Check for model or property release notes if people or recognizable property appear.
4. Save a copy of the license text or a screenshot with the date, so you can show what terms applied when you downloaded it.

How to verify a photo's license before publishing

A short, repeatable routine prevents most copyright problems.

1. Identify the original source. Trace the image back past Pinterest, reposts, and aggregators to the site that actually licenses it.
2. Read the license, not the caption. "Free" in a caption is not a license. Look for the terms page.
3. Match the license to your use. A license that covers a personal blog may not cover a paid ad or a product for sale.
4. Check the people and places. If a face or a logo is visible, confirm whether a release is included and whether your context is permitted.
5. Record your evidence. Keep the source URL, license text, and download date.
6. Re-check if you change the use. A new context — print, merchandise, paid media — can fall outside the original license.

Common mistakes that lead to copyright issues

• Assuming "royalty-free" means "no rules." It means no per-use royalties. The license still limits how you use the image.
• Trusting a search result's license label. Aggregators and search engines sometimes mislabel images. The source license is authoritative.
• Using a free image commercially without checking. Many free tiers exclude commercial use or require attribution.
• Treating public domain and royalty-free as interchangeable. They are different legal states with different obligations.
• Ignoring people and property. A valid photo license does not equal a model or property release.
• Forgetting to keep proof. If a dispute arises later, your license record is your defense.
• Reusing an image in a new medium without re-reading the terms. Rights that cover a blog post may not cover a billboard or a product.

If you cannot find clear license terms for an image, the safe move is to choose a different image rather than publish and hope.