<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Nawal Shrestha</title>
    <description>The latest articles on DEV Community by Nawal Shrestha (@nawalshrestha).</description>
    <link>https://dev.to/nawalshrestha</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4160809%2Fef25d13b-f6fd-408d-a12a-eb7a5b3ba956.png</url>
      <title>DEV Community: Nawal Shrestha</title>
      <link>https://dev.to/nawalshrestha</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nawalshrestha"/>
    <language>en</language>
    <item>
      <title>JPEG Quality vs File Size: What the Slider Really Does</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Sat, 14 Nov 2026 04:27:12 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/jpeg-quality-vs-file-size-what-the-slider-really-does-eki</link>
      <guid>https://dev.to/nawalshrestha/jpeg-quality-vs-file-size-what-the-slider-really-does-eki</guid>
      <description>&lt;h1&gt;
  
  
  JPEG Quality vs File Size: What the Slider Really Does
&lt;/h1&gt;

&lt;p&gt;Open any image editor, export a photo at quality 90, then export the same photo at quality 80. The second file is often a third smaller, and you cannot see the difference. Export it again at 60 and the file barely shrinks further, but the photo starts to look rough. That uneven trade is the whole story of JPEG quality vs file size, and once you see the shape of it, the slider stops feeling random.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the JPEG quality number controls
&lt;/h2&gt;

&lt;p&gt;The quality number controls how aggressively the encoder throws away detail. A JPEG stores an image as blocks of frequency data, and the quality setting picks a quantization table that decides how much of that data to keep. A high number keeps more detail and makes a bigger file. A low number discards more and makes a smaller one.&lt;/p&gt;

&lt;p&gt;The number runs from 1 to 100 in most editors, but the scale is not a percentage of anything. Quality 50 does not mean half the detail is gone. It means the encoder picked the middle table from a set that the JPEG standard defined decades ago, and the tables at the top end are much closer together than the ones at the bottom.&lt;/p&gt;

&lt;h2&gt;
  
  
  JPEG quality vs file size: why the curve bends
&lt;/h2&gt;

&lt;p&gt;JPEG quality vs file size follows a curve that flattens fast. Dropping from 95 to 85 can cut a file by a third or more, because the encoder is discarding detail you barely notice. Dropping from 60 to 50 saves far less, because most of the discardable detail is already gone, and what remains is the structure your eyes see.&lt;/p&gt;

&lt;p&gt;Rough figures for a typical 12-megapixel phone photo. Yours will differ, because content matters more than the setting, but the shape of the curve holds for nearly every photo.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Quality&lt;/th&gt;
&lt;th&gt;Rough file size&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;95&lt;/td&gt;
&lt;td&gt;5-7 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;90&lt;/td&gt;
&lt;td&gt;3-4 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;85&lt;/td&gt;
&lt;td&gt;2-3 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;80&lt;/td&gt;
&lt;td&gt;1.5-2.5 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;70&lt;/td&gt;
&lt;td&gt;1-1.5 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;60&lt;/td&gt;
&lt;td&gt;0.8-1.2 MB&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The top of the scale is where the savings live, and the bottom is where the damage shows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why two photos at quality 80 have different sizes
&lt;/h2&gt;

&lt;p&gt;Two photos exported at quality 80 can differ threefold, because JPEG compresses detail and photos hold different amounts of it. A clear sky compresses to almost nothing. A forest full of leaves barely compresses at all. Grain is the worst case: a high-ISO shot stays large at any quality setting, because the encoder treats the grain as detail worth keeping.&lt;/p&gt;

&lt;p&gt;This is why a single recommended setting never works for every photo. A product shot on a white background and a concert photo in low light are different compression problems, and the same number treats them as if they were the same. Judge the setting on your own images, not on a chart.&lt;/p&gt;

&lt;h2&gt;
  
  
  JPEG quality vs file size in practice: the settings worth memorizing
&lt;/h2&gt;

&lt;p&gt;75 to 85 covers nearly everything for photos on the web. Above 90 you pay for detail nobody can see. Below 60 you start seeing blocky patches in skies. Thumbnails can go lower, since nobody inspects a 200-pixel image. Archives stay at 90 or above, because storage is cheap and re-encoding a low-quality file later makes things worse.&lt;/p&gt;

&lt;p&gt;Screenshots are the exception. Text and flat colors compress badly as JPEG, and quality 80 on a screenshot shows smudges around every letter. Save screenshots as PNG or WebP, and keep JPEG for photos.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to pick a number instead of guessing
&lt;/h2&gt;

&lt;p&gt;Export the same photo at 90, 80, and 70, then compare the three at 100 percent. Pick the lowest setting where you cannot spot a difference. That test takes two minutes and beats every rule of thumb, because it uses your photo instead of someone else's. When the limit is a number of kilobytes, a target-size tool earns its place.&lt;/p&gt;

&lt;p&gt;I wrote a longer walkthrough of &lt;a href="https://getsnapshrink.com/blog/how-to-compress-jpeg-file-size/" rel="noopener noreferrer"&gt;compressing JPEGs without visible loss&lt;/a&gt; if you want the full process with examples. When the limit is a number rather than a look, &lt;a href="https://getsnapshrink.com/compress-image-to-100kb/" rel="noopener noreferrer"&gt;SnapShrink's exact-KB compressor&lt;/a&gt; aims at the number you type and finds the highest quality that fits under it. The slider is a fine tool for a look. A target size is the right tool for a number.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions about JPEG quality
&lt;/h2&gt;

&lt;p&gt;Three questions come up whenever this topic shows up in a thread, so here are the short answers. The sections above cover the mechanism; these cover the edge cases people run into when they start changing quality settings on files they care about.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does lowering JPEG quality damage the original?
&lt;/h3&gt;

&lt;p&gt;Only if you overwrite it. Export to a new file and the original stays untouched. Work on a copy whenever the photo matters, because quality lost in a re-encode never comes back.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is quality 100 the same as the original?
&lt;/h3&gt;

&lt;p&gt;No. JPEG always discards some data, even at 100. The file is large and the loss is invisible, but it is still lossy. If you need every pixel preserved, use PNG or keep the RAW file.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does resizing matter more than quality?
&lt;/h3&gt;

&lt;p&gt;Often, yes. Halving the width and height removes three quarters of the pixels, and no quality setting can match that. Resize first to the size you need, then tune quality. Doing it the other way round wastes effort on pixels nobody will see.&lt;/p&gt;

&lt;p&gt;The slider stops feeling random once you know the curve. High numbers buy detail you cannot see. Low numbers cost detail you can. Test your own photo at three settings, keep the lowest one that still looks right, and let a target-size tool handle the days when the limit is a number.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>images</category>
      <category>tutorial</category>
      <category>webperf</category>
    </item>
    <item>
      <title>Bulk Image Compressor: When to Use CLI vs the Browser</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Wed, 11 Nov 2026 04:26:40 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/bulk-image-compressor-when-to-use-cli-vs-the-browser-1571</link>
      <guid>https://dev.to/nawalshrestha/bulk-image-compressor-when-to-use-cli-vs-the-browser-1571</guid>
      <description>&lt;h1&gt;
  
  
  Bulk Image Compressor: When to Use CLI vs the Browser
&lt;/h1&gt;

&lt;p&gt;You get the folder the same way every time. Someone exports a few hundred images straight out of a camera or a design tool, and now they are yours to shrink before the site can use them. A bulk image compressor is the obvious answer, but it comes in two shapes, and picking the wrong one turns a ten-minute job into an afternoon.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a bulk image compressor does under the hood
&lt;/h2&gt;

&lt;p&gt;It takes a folder of images and re-encodes each one at a smaller size. It decodes the file, applies a quality setting or a target size, resizes it if you ask, strips metadata like EXIF, and writes out a new file. The good ones work without uploading anything, and the fast ones process dozens of files in parallel.&lt;/p&gt;

&lt;p&gt;Two things decide how good the result looks. The first is the encoder doing the work. The second is whether the tool lets you aim at a size instead of guessing a quality number. A tool that only offers a quality slider leaves you checking file sizes by hand after every run, and that checking is where the afternoon goes.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the command line wins
&lt;/h2&gt;

&lt;p&gt;The command line wins when the job repeats. If you compress images every week, or the same folder gets rebuilt on every deploy, a script beats a drag-and-drop window. You write the command once, save it, and the next run takes seconds. That repeatability is the whole argument, and for a scheduled job there is no real contest.&lt;/p&gt;

&lt;p&gt;ImageMagick handles the common case in one line:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mogrify -resize 1600x1600 -quality 80 -strip *.jpg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That resizes every JPEG to fit inside 1600 pixels, re-encodes at quality 80, and strips the metadata. One warning: mogrify overwrites your files in place, so copy the folder first. I learned that the polite way, by reading the docs, and I would rather you learn it from this sentence than from a missing original.&lt;/p&gt;

&lt;p&gt;For a pipeline that needs more control, a short Node script with sharp does the same job and plugs into a build step:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;sharp&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;require&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'sharp'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;fs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;require&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'fs'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;file&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="n"&gt;fs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;readdirSync&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'./photos'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;sharp&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`./photos/${file}`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;resize&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1600&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;jpeg&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;quality&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;80&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toFile&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sb"&gt;`./web/${file}`&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That script is boring, and boring is the point. It runs the same way on every deploy, and it fails loudly instead of silently producing files at the wrong size.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a bulk image compressor in the browser wins
&lt;/h2&gt;

&lt;p&gt;The browser wins when the job is a one-off and the folder is already on your machine. You open the page, drop the files in, set a size, and download the results. There is nothing to install, nothing to update, and no script to debug. For a folder you will touch once, skipping setup is the entire point.&lt;/p&gt;

&lt;p&gt;The other advantage is privacy, with one condition: the tool has to process files locally. &lt;a href="https://getsnapshrink.com/bulk-image-compressor/" rel="noopener noreferrer"&gt;SnapShrink's bulk image compressor&lt;/a&gt; runs the whole job in your browser, so the files never leave your machine. A server-side uploader is a different deal, and for client photos or unreleased product shots, that difference matters. If you only need one image under an exact limit instead of a whole folder, the &lt;a href="https://getsnapshrink.com/compress-image/" rel="noopener noreferrer"&gt;main compressor&lt;/a&gt; takes a target size in kilobytes and aims at that number directly.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to pick in thirty seconds
&lt;/h2&gt;

&lt;p&gt;Four questions settle the choice, and you can answer them before you open any tool. Frequency matters most: a job you repeat deserves a script, and a job you do once deserves the fastest path to done. Volume, privacy, and repeatability fill in the rest, and together they point at one of the two routes without much debate.&lt;/p&gt;

&lt;p&gt;Privacy deserves a note of its own. A browser tool that processes files locally and a CLI tool both keep your images on your machine. A server-side uploader sends them somewhere else, and for client work that distinction is worth checking before you drag a folder in.&lt;/p&gt;

&lt;h2&gt;
  
  
  What can go wrong
&lt;/h2&gt;

&lt;p&gt;Most batch compression regret comes from a few mistakes, and all of them are easy to avoid. Overwriting originals tops the list. Resizing without keeping the aspect ratio produces stretched images. Forgetting to strip metadata is the quiet one: a phone photo can carry location data, and that data survives compression unless you remove it.&lt;/p&gt;

&lt;p&gt;A dry run on three files catches all of these. Compress a small sample, check the sizes, open one image at full size, and confirm the originals are still where you left them. The whole check takes two minutes, and it is the cheapest insurance in this workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  A workflow that uses both
&lt;/h2&gt;

&lt;p&gt;Most teams end up using both routes, and that is the sensible outcome rather than a failure to decide. The build pipeline gets a script, because deploys should never depend on someone remembering to compress images. The one-off folder from a client gets the browser tool, because scripting a job you will do once wastes a good afternoon.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions I hear about batch compression
&lt;/h2&gt;

&lt;p&gt;The same three questions come up every time I write about this, so here are the short answers. The details above cover the how; these cover the worries people have before they run a batch job on files they care about.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does batch compression reduce quality?
&lt;/h3&gt;

&lt;p&gt;Yes, if you use lossy settings, and no, if you only resize or strip metadata. Quality 80 JPEG looks the same as the original to most eyes on a screen. Keep a copy of the originals either way, because you cannot get quality back once it is gone.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I compress images without uploading them?
&lt;/h3&gt;

&lt;p&gt;Yes. A browser tool that processes files locally never sends them anywhere, and a CLI tool never touches a network at all. Check for that before you use any online converter on client work. The Network tab in DevTools shows you the truth in about ten seconds.&lt;/p&gt;

&lt;h3&gt;
  
  
  What quality setting should I start with?
&lt;/h3&gt;

&lt;p&gt;Start at 80 for JPEG photos. If the file is still too big, drop to 70 and look at the result at full size. If it looks fine at 70, try 60. Most photos land somewhere in that range, and the exact number depends on how much detail the photo holds.&lt;/p&gt;

&lt;p&gt;Next time the folder lands in your inbox, ask one question before you open anything: will I do this again? A yes means you write the script once and never think about it again. A no means you drop the folder in the browser, download the results, and move on. Either way the images get smaller, and you get your afternoon back.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>images</category>
      <category>tutorial</category>
      <category>performance</category>
    </item>
    <item>
      <title>Compress Image to Exact KB: How Target-Size Encoding Works</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Sat, 07 Nov 2026 04:26:32 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/compress-image-to-exact-kb-how-target-size-encoding-works-46bd</link>
      <guid>https://dev.to/nawalshrestha/compress-image-to-exact-kb-how-target-size-encoding-works-46bd</guid>
      <description>&lt;h1&gt;
  
  
  Compress Image to Exact KB: How Target-Size Encoding Works
&lt;/h1&gt;

&lt;p&gt;The form says the photo must be under 100KB. Yours is 104KB. You drag the quality slider down a little, export, and get 97KB, but the face looks soft. You nudge it back up, export again, and land on 103KB. Rejected again. Twenty minutes later you have six versions of the same photo and no idea which slider position gives the best quality that still fits.&lt;/p&gt;

&lt;p&gt;That loop is the whole problem with compressing by hand. You need to compress image to exact KB, a hard number, using a control that was never designed to hit a number. Target-size encoding flips the job around: you name the size, and the tool searches for the highest quality that fits under it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compress image to exact KB: why the slider fails
&lt;/h2&gt;

&lt;p&gt;A quality slider controls how aggressively the encoder discards detail, but it does not control file size directly, and the relationship is not linear. Dropping quality from 90 to 80 might cut a photo by 40 percent, while the same move on a textured image might cut it by 10 percent.&lt;/p&gt;

&lt;p&gt;That unpredictability is why manual guessing eats an afternoon. Each export is a guess, each guess teaches you almost nothing about the next one, and the result you finally accept is rarely the best quality that fits. It is just the first one that happened to land under the cap. A tool that searches instead of guessing removes the loop entirely.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compress image to exact KB with binary search
&lt;/h2&gt;

&lt;p&gt;Target-size encoding treats quality as a search problem. The engine picks a quality level, encodes, and checks the size. Too big, it tries lower. Under the cap with room to spare, it tries higher, repeating until it finds the highest quality that fits, usually in six to eight encodes.&lt;/p&gt;

&lt;p&gt;A worked example makes the search concrete. Take a portrait that starts at 1.8MB as a JPEG. The target is 100KB. The engine tries quality 90 first and gets 210KB, too big. It tries 70 and gets 88KB, under the cap but with room wasted. Then it splits the difference at 80 and gets 112KB, still too big, then 75 and gets 98KB. One more check at 77 gives 101KB, just over, so the search settles on 75 at 98KB. Every step is automatic, and the answer is the best quality the cap allows rather than the first one that happened to fit.&lt;/p&gt;

&lt;p&gt;SnapShrink's &lt;a href="https://getsnapshrink.com/compress-image-to-100kb/" rel="noopener noreferrer"&gt;target-KB compressor&lt;/a&gt; runs exactly this search in the browser: type 100 in the Target KB field, pick an output format, and the before and after sizes confirm the file came in under the cap. If quality alone cannot reach the cap, the engine gently downscales the image and searches again, rather than handing you a file that misses the limit.&lt;/p&gt;

&lt;h2&gt;
  
  
  When the cap is unreachable, and what to change first
&lt;/h2&gt;

&lt;p&gt;Some images cannot reach a small cap at any quality without turning to mush. A detailed landscape at full camera resolution will not fit under 100KB and still look like itself. When that happens, change things in this order, because each step buys more quality than the one after it.&lt;/p&gt;

&lt;p&gt;First, resize to the size the destination actually displays. A portal that shows a photo at 600 pixels wide does not need a 4000-pixel source, and resizing alone can cut the file by more than half before quality even enters the picture. Second, crop empty borders and background so the quality budget goes to faces and text instead of sky. Third, switch formats if the destination allows it: WebP usually reaches the same cap at visibly better quality than JPEG, while PNG is the wrong choice for photos under a cap because it stores pixels losslessly. Only after those three steps should you accept a lower quality, because by then you have removed waste instead of detail.&lt;/p&gt;

&lt;p&gt;A good tool tells you when it has hit this wall instead of failing silently. If the smallest achievable size is still over the cap, that number is useful information: it tells you to resize or crop and try again, rather than exporting the same doomed photo a seventh time.&lt;/p&gt;

&lt;h2&gt;
  
  
  A checklist before you upload
&lt;/h2&gt;

&lt;p&gt;Run through this short check before submitting, and the form stops bouncing your photo back. Size, format, dimensions, and a full-zoom look at faces and text cover nearly every rejection reason a portal gives. It takes two minutes and saves a second upload round.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Confirm the file is under the cap with margin to spare. Portals measure bytes, and 100.4KB rounds to a rejection.&lt;/li&gt;
&lt;li&gt;Confirm the format matches what the portal accepts. A WebP under the cap still fails on a form that only lists JPG and PNG.&lt;/li&gt;
&lt;li&gt;Confirm the dimensions meet the portal's minimum. Some forms reject images that are small enough but too low resolution, which is a different error with the same unhelpful message.&lt;/li&gt;
&lt;li&gt;Open the final file at full zoom and check faces and any text. If either looks soft, resize or crop and run the search again rather than accepting the first version that fits.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One more habit pays off across every portal you will ever use: keep the original. Portals change their caps, a 100KB version made for one form is the wrong size for the next, and re-encoding from an already compressed file throws away detail twice. Archive the original, generate each capped version fresh from it, and the next form takes two minutes instead of twenty.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is a 100KB photo going to look bad?
&lt;/h3&gt;

&lt;p&gt;It depends on the source. A modest portrait at display size usually looks fine under 100KB. A huge, detailed landscape will look softer, because you are removing most of its data. Resize first and the same cap buys visibly better quality.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I compress a batch to the same KB target?
&lt;/h3&gt;

&lt;p&gt;Yes. Drop the batch, set the target once, and each file gets its own search, since a flat portrait and a busy landscape need different quality levels to hit the same cap. Download the results as a ZIP when the batch finishes.&lt;/p&gt;

&lt;h3&gt;
  
  
  What if my photo cannot reach the target at all?
&lt;/h3&gt;

&lt;p&gt;Resize it to the display size, crop empty borders, and switch to WebP if the portal allows it, then run the search again. If the tool reports the smallest size it achieved, use that number to judge how much more you need to cut.&lt;/p&gt;

&lt;p&gt;That 104KB photo from the start of this article takes about a minute now: type 100 into the &lt;a href="https://getsnapshrink.com/compress-image-to-100kb/" rel="noopener noreferrer"&gt;target-KB compressor&lt;/a&gt;, let the search find the best quality that fits, check the face at full zoom, and upload. The slider loop is gone, and the version you submit is the best one the cap allows, not the first one that happened to squeak under it.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>images</category>
      <category>tutorial</category>
      <category>performance</category>
    </item>
    <item>
      <title>HEIC to JPG on Windows: A Developer's Survival Guide</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Wed, 04 Nov 2026 04:26:10 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/heic-to-jpg-on-windows-a-developers-survival-guide-43a2</link>
      <guid>https://dev.to/nawalshrestha/heic-to-jpg-on-windows-a-developers-survival-guide-43a2</guid>
      <description>&lt;h1&gt;
  
  
  HEIC to JPG on Windows: A Developer's Survival Guide
&lt;/h1&gt;

&lt;p&gt;The photos arrive in a shared folder: 40 shots from an iPhone, ready for a client gallery. On your Windows machine, half the thumbnails are blank, the upload form rejects every .heic file, and the one viewer that opens them wants a codec pack from the Microsoft Store. Nothing is corrupt. The files are just in a format Windows still treats as a stranger, and the fix is a conversion you can run without installing anything.&lt;/p&gt;

&lt;p&gt;Converting to JPG is the conversion that unblocks this exact mess. JPG opens everywhere, forms accept it, and every editor built in the last twenty years reads it. This guide covers why Windows chokes on HEIC, when JPG beats PNG as the target, and a batch workflow that gets 40 photos uploaded without a codec install.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Windows still chokes on HEIC files
&lt;/h2&gt;

&lt;p&gt;HEIC is Apple's default iPhone photo format since iOS 11, built on the HEIF container with HEVC encoding inside. Windows 10 and 11 do not ship the HEIF codec by default, so Explorer, older editors, and many upload forms do not recognise the files.&lt;/p&gt;

&lt;p&gt;That last point is the one developers miss. A codec install is a local fix for a distribution problem. The moment a photo leaves your machine, it meets machines and forms you do not control. Conversion solves the distribution problem instead: the JPG you send opens on the recipient's machine whether or not they installed anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  HEIC to JPG or HEIC to PNG: pick by what happens next
&lt;/h2&gt;

&lt;p&gt;HEIC to JPG is the right target when the photo is headed for sharing, a form upload, email, or a CMS. JPG files stay small, every destination accepts them, and quality loss at 85 to 90 is invisible at normal sizes. HEIC to PNG fits further editing, where lossless pixels matter.&lt;/p&gt;

&lt;p&gt;The tradeoff runs in opposite directions, so do not mix them up. JPG trades a little quality for a much smaller file. PNG keeps every pixel but can balloon: a 2MB HEIC often expands to 15MB or more as PNG, because PNG stores decoded pixels without HEIC's compression. If a form caps file size, PNG is the wrong target even though it is the lossless one. For a longer discussion of that size surprise, SnapShrink's &lt;a href="https://getsnapshrink.com/heic-to-png/" rel="noopener noreferrer"&gt;HEIC to PNG converter&lt;/a&gt; page spells out the numbers. For sharing and uploads, convert to JPG and keep the HEIC original archived.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;The photo is headed for&lt;/th&gt;
&lt;th&gt;Convert to&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A form, email, chat, or CMS upload&lt;/td&gt;
&lt;td&gt;JPG&lt;/td&gt;
&lt;td&gt;Accepted everywhere, small file&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Further editing, cropping, or colour work&lt;/td&gt;
&lt;td&gt;PNG&lt;/td&gt;
&lt;td&gt;Lossless pixels, editing headroom&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A size-capped portal&lt;/td&gt;
&lt;td&gt;JPG&lt;/td&gt;
&lt;td&gt;PNG often exceeds the cap on its own&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Archiving the original&lt;/td&gt;
&lt;td&gt;Neither, keep the HEIC&lt;/td&gt;
&lt;td&gt;Every conversion throws away the option to redo it&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  HEIC to JPG in batch: the workflow that actually works
&lt;/h2&gt;

&lt;p&gt;Converting one photo is trivial. Converting 40 without losing track of which ones are done is where the process falls apart. The workflow below keeps the batch organised: one folder in, one ZIP out, and three spot checks before anything uploads.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Copy the HEIC files into a single folder and sort by name, so the converted set matches the original set one to one.&lt;/li&gt;
&lt;li&gt;Open a &lt;a href="https://getsnapshrink.com/heic-to-jpg/" rel="noopener noreferrer"&gt;HEIC to JPG converter that runs in the browser&lt;/a&gt;, drop the whole folder in, and set JPG output. SnapShrink's version decodes HEIC in the tab, so the photos never upload anywhere, which matters when the folder holds client work.&lt;/li&gt;
&lt;li&gt;Set quality 85 to 90 for photos headed to the web. Below 80, skies and smooth gradients start to band. Above 90, the file grows fast for a difference nobody sees at normal sizes.&lt;/li&gt;
&lt;li&gt;Download the batch as a ZIP, unzip into a folder next to the originals, and spot check three files at full zoom: one portrait, one landscape, one with text or fine detail in it.&lt;/li&gt;
&lt;li&gt;Upload the JPGs. Keep the HEIC folder. If a destination later wants WebP or PNG, convert from the HEIC again, never from the JPG, because each lossy pass throws away detail you cannot get back.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One check worth doing before you send anything on: open DevTools, go to the Network tab, and run a conversion. If the network stays quiet, the file never left your machine. Most free converters upload your photos to a server first. For a meme that does not matter. For client photos it is a privacy decision you should make deliberately, not by default.&lt;/p&gt;

&lt;h2&gt;
  
  
  What breaks during conversion
&lt;/h2&gt;

&lt;p&gt;Three things catch people out during conversion: Live Photos and bursts, metadata loss, and orientation or colour handling. All three are avoidable once you know where each one bites, and none of them requires special software to work around. Each one gets its own fix below.&lt;/p&gt;

&lt;p&gt;First, Live Photos and bursts. A HEIC file can carry extra frames, and a converter typically takes the primary still image. If you need every frame of a burst, export the burst from the Photos app first and convert the frames individually.&lt;/p&gt;

&lt;p&gt;Second, metadata. Location and device EXIF data generally does not survive conversion, and Apple-specific metadata goes with it. For most uploads that is a bonus, since you probably did not want location data attached to a client gallery anyway. If you need metadata preserved, say so before converting, because you cannot recover it from the JPG afterwards.&lt;/p&gt;

&lt;p&gt;Third, orientation and colour. HEIC stores orientation as metadata, and a converter that ignores it hands you a sideways photo. A decent converter applies the orientation during decode, so the JPG comes out the right way up. That is one of the three files worth checking in step 4 above: if a portrait comes out sideways, the tool is at fault, not the photo.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Do I need the HEIF codec pack to convert?
&lt;/h3&gt;

&lt;p&gt;No. A browser-based converter decodes HEIC in the tab using the browser's own decoder, so Windows never needs to understand the format. The codec pack only fixes previews in Explorer and other native apps.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will the JPG look worse than the HEIC?
&lt;/h3&gt;

&lt;p&gt;At quality 85 to 90, a photo looks the same at normal viewing sizes. The file gets bigger than the HEIC, because JPG compresses less efficiently, and fine text is where a difference would show first. Check text areas at full zoom before you send the file on.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I stop new iPhone photos from saving as HEIC?
&lt;/h3&gt;

&lt;p&gt;Yes. On the iPhone, go to Settings, Camera, Formats, and choose Most Compatible. New photos save as JPG from then on. Photos already on the device stay HEIC until you convert them.&lt;/p&gt;

&lt;p&gt;Back to that folder of 40 blank thumbnails. Convert the batch to JPG, keep the HEIC originals, and send the JPGs. The next person who opens them will see photos, not an error, and nobody has to install a codec to do it.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>images</category>
      <category>tutorial</category>
      <category>windows</category>
    </item>
    <item>
      <title>AVIF to JPG Conversion: The Fallback Every Developer Needs</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Sat, 31 Oct 2026 04:26:11 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/avif-to-jpg-conversion-the-fallback-every-developer-needs-1nf3</link>
      <guid>https://dev.to/nawalshrestha/avif-to-jpg-conversion-the-fallback-every-developer-needs-1nf3</guid>
      <description>&lt;h1&gt;
  
  
  AVIF to JPG Conversion: The Fallback Every Developer Needs
&lt;/h1&gt;

&lt;p&gt;You download an image a client sent, double-click it, and your editor refuses to open it. The extension reads .avif. Nothing is corrupt. The file is just in a format your tooling does not speak yet, and the form you need to upload it to does not either.&lt;/p&gt;

&lt;p&gt;AVIF is the newer, smaller format. JPG is the format everything accepts. Converting AVIF to JPG is the fallback you reach for when compatibility matters more than file size, and it takes about a minute when you know what to watch.&lt;/p&gt;

&lt;h2&gt;
  
  
  When does AVIF to JPG conversion make sense?
&lt;/h2&gt;

&lt;p&gt;AVIF to JPG conversion makes sense whenever the destination cannot read AVIF: older CMS uploads, print shops, email clients, form portals, and editors with frozen format support. JPG opens everywhere, so converting unblocks an upload without asking the sender to re-export. Keep the AVIF original archived, since JPG conversion is a one-way trip to a larger, lossier file.&lt;/p&gt;

&lt;p&gt;AVIF files usually arrive from three places. Chrome saves some downloaded images as AVIF, Android phones can capture in AVIF, and CDNs like Cloudflare convert images to AVIF automatically. So when a downloaded image will not open in your editor, check the extension before assuming the file is damaged. It is probably AVIF, and the fix is a conversion, not a re-download.&lt;/p&gt;

&lt;h2&gt;
  
  
  AVIF to JPG quality: what actually changes
&lt;/h2&gt;

&lt;p&gt;Converting AVIF to JPG always recompresses the image, because JPG is lossy and cannot hold AVIF's data untouched. At quality 85 to 90, the visible difference on a photo is usually nil, but the file grows, since AVIF's compression is roughly twice as efficient as JPG. Text and hard edges suffer first, so check those areas after converting.&lt;/p&gt;

&lt;p&gt;That tradeoff is the whole decision in one paragraph. AVIF wins on size, JPG wins on compatibility, and nothing wins on both. If the destination accepts WebP, convert to WebP instead: it keeps files much smaller than JPG while opening in far more apps than AVIF. JPG stays the fallback for destinations that accept nothing else.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to convert AVIF to JPG without uploading anything
&lt;/h2&gt;

&lt;p&gt;Most online converters upload your file to a server, convert it there, and hand it back. For a client asset or an unreleased product shot, that upload is a privacy decision you might not want to make. SnapShrink's &lt;a href="https://getsnapshrink.com/avif-to-jpg/" rel="noopener noreferrer"&gt;AVIF to JPG converter&lt;/a&gt; decodes AVIF in your browser, so the file never leaves your computer.&lt;/p&gt;

&lt;p&gt;The steps are short:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the tool. JPG output is pre-selected.&lt;/li&gt;
&lt;li&gt;Drop in one or more .avif files. A batch converts the same way as a single file, and you can download the results individually or as a ZIP.&lt;/li&gt;
&lt;li&gt;Set the quality slider, or set a Target KB if the destination has a file-size limit. Quality 85 to 90 is a good default for photos.&lt;/li&gt;
&lt;li&gt;Check the converted JPG at full zoom, especially any text or hard edges, then upload the JPG and archive the AVIF.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can verify the no-upload claim yourself in about ten seconds: open DevTools, go to the Network tab, and run a conversion. If the network stays quiet, the file never left your machine. Chrome, Edge, and Firefox can decode AVIF natively; if your browser cannot, the tool says so plainly instead of failing silently.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the AVIF original
&lt;/h2&gt;

&lt;p&gt;The one rule that matters after converting: never treat the JPG as your master. JPG is lossy, so converting back from JPG to AVIF later cannot recover what the JPG pass threw away. It just wraps a degraded image in a modern container.&lt;/p&gt;

&lt;p&gt;The workflow that holds up is boring on purpose. Archive the AVIF original. Convert a JPG copy for the destination that demands it. If a second destination wants WebP, convert from the AVIF again, not from the JPG. Originals stay originals, derivatives stay disposable, and no destination ever forces a quality loss on the rest.&lt;/p&gt;

&lt;h3&gt;
  
  
  FAQ
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Will the JPG look worse than the AVIF?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;At quality 85 to 90, a photo usually looks identical. The file gets bigger, and fine text or hard edges are where a difference would show first, so check those before you send it on.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I convert a batch of AVIF images at once?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Yes. Drop multiple .avif files, set output to JPG, and download them individually or as a ZIP when the batch finishes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What if my browser cannot decode AVIF?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Use Chrome or Edge, which decode AVIF natively. The converter shows a clear message when the browser cannot decode the format, so you are not left guessing.&lt;/p&gt;

&lt;p&gt;Next time an .avif bounces off a form, convert a JPG copy, upload that, and keep the AVIF in your archive. The small file stays small, the upload goes through, and the next destination that demands a different format gets its own fresh conversion from the original. That is the entire fallback workflow, and the &lt;a href="https://getsnapshrink.com/avif-to-jpg/" rel="noopener noreferrer"&gt;AVIF to JPG converter&lt;/a&gt; runs it in your browser for free.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>images</category>
      <category>tutorial</category>
      <category>webperf</category>
    </item>
    <item>
      <title>Shopify Image Optimizer Checklist for Product Photos</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Wed, 28 Oct 2026 04:26:12 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/shopify-image-optimizer-checklist-for-product-photos-58pl</link>
      <guid>https://dev.to/nawalshrestha/shopify-image-optimizer-checklist-for-product-photos-58pl</guid>
      <description>&lt;h1&gt;
  
  
  Shopify Image Optimizer Checklist for Product Photos
&lt;/h1&gt;

&lt;p&gt;You finish a product shoot, export 40 photos, upload them to Shopify, and the collection page crawls on a phone. Nothing is broken. The theme is fine, the apps are fine. The photos are just too heavy, and every one of them loads at full camera resolution.&lt;/p&gt;

&lt;p&gt;That is the usual state of a Shopify store's images, and it is fixable with a short checklist. A Shopify image optimizer preset handles the repetitive part: resize, re-encode, and cap the file weight before the photo ever reaches Shopify. The rest is knowing which settings to pick and which mistakes to avoid.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does a Shopify image optimizer preset do?
&lt;/h2&gt;

&lt;p&gt;A Shopify image optimizer preset applies a fixed set of export rules to a product photo: fit the long edge inside 2048 pixels, encode it as WebP, and search for the highest quality under a weight cap, 300KB in SnapShrink's preset. You drop in camera files and get back store-ready images without touching a quality slider per photo.&lt;/p&gt;

&lt;p&gt;Shopify accepts images up to 4472 by 4472 pixels, but that ceiling is not a target. A product photo displayed at 800 pixels wide on a collection grid gains nothing from a 4000-pixel source. The 2048-pixel fit keeps zoom sharp on retina screens while cutting the pixels Shopify has to serve by more than half compared with a straight camera export.&lt;/p&gt;

&lt;h2&gt;
  
  
  Shopify image optimizer settings: size, format, and weight
&lt;/h2&gt;

&lt;p&gt;For product photos, export at 2048 pixels on the long edge, WebP format, and a weight cap of 300KB per image. That combination keeps zoom sharp, keeps each file predictable, and works in every modern browser. PNG stays reserved for graphics with hard edges, and JPEG stays the fallback for tools that cannot read WebP.&lt;/p&gt;

&lt;p&gt;The three settings do different jobs, so it helps to set them in order. Size first: if the layout never shows the photo wider than 1200 pixels, a 2048-pixel master still leaves room for zoom without shipping camera-sized files. Format second: WebP cuts roughly a quarter to a third off an equivalent JPEG for photos, which is the single biggest saving most stores leave on the table. Weight last: a 300KB cap is a ceiling, not a goal. Flat product shots on white backgrounds often land well under it, and that is fine.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Photo type&lt;/th&gt;
&lt;th&gt;Export settings&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Product photo on white or lifestyle background&lt;/td&gt;
&lt;td&gt;2048px, WebP, max 300KB&lt;/td&gt;
&lt;td&gt;Sharp zoom, predictable weight&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Logo, badge, or graphic with hard edges&lt;/td&gt;
&lt;td&gt;PNG, original size&lt;/td&gt;
&lt;td&gt;WebP and JPEG both soften hard edges at low quality&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Photo headed to an old tool or email&lt;/td&gt;
&lt;td&gt;JPEG, quality 80 to 85&lt;/td&gt;
&lt;td&gt;Opens everywhere, still reasonably small&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How Shopify's CDN and srcset fit in
&lt;/h2&gt;

&lt;p&gt;Shopify serves product images through its CDN, which generates resized variants from the file you upload, and your theme's srcset markup picks the variant per screen. That pipeline works best with a sane master: a 2048-pixel WebP gives the CDN a source for every variant, while a 6MB camera file makes every variant heavier than it needs to be.&lt;/p&gt;

&lt;p&gt;One practical check after upload: open the collection page in DevTools, filter the Network tab by Img, and sort by size. If any product image still shows up in megabytes, that product is still serving its original file, and it is the one to fix first.&lt;/p&gt;

&lt;h2&gt;
  
  
  The checklist, start to finish
&lt;/h2&gt;

&lt;p&gt;The full pass takes about ten minutes per product once the preset is set up: start from the original file, fit the long edge and encode, check the result at full zoom, then upload and confirm the product page uses the new file.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start from the highest-quality original. Never re-export from a file you already compressed for another channel, since each lossy pass throws away detail you cannot get back.&lt;/li&gt;
&lt;li&gt;Fit the long edge to 2048 pixels and keep the photo's own aspect ratio. Do not force square crops unless your theme actually requires them.&lt;/li&gt;
&lt;li&gt;Encode WebP with a 300KB weight cap. SnapShrink's &lt;a href="https://getsnapshrink.com/presets/shopify-image-optimizer/" rel="noopener noreferrer"&gt;Shopify image optimizer preset&lt;/a&gt; applies steps 2 and 3 in one pass, in your browser, with nothing uploaded.&lt;/li&gt;
&lt;li&gt;Check the result at full zoom before you upload it. Look at edges, fabric texture, and any text on packaging, since those are the first places over-compression shows.&lt;/li&gt;
&lt;li&gt;Name the file descriptively, like walnut-desk-organizer-front.webp. It keeps your media library searchable and gives search engines a readable filename.&lt;/li&gt;
&lt;li&gt;Add alt text in Shopify admin after upload. Describe the product, not the filename, since alt text is what screen readers and image search actually read.&lt;/li&gt;
&lt;li&gt;Upload the optimized file to the product and confirm the product page uses it, not the older original still sitting in your files.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Three mistakes that undo the work
&lt;/h2&gt;

&lt;p&gt;The first is uploading the optimized photo and then letting the product keep pointing at the original. Shopify keeps both files, so check the product page after you swap and confirm the new file is the one actually serving on the page.&lt;/p&gt;

&lt;p&gt;The second is saving photos as PNG out of habit. PNG is the right call for logos and graphics, but a product photo saved as PNG can weigh several times its WebP version, and that weight lands on every shopper who opens the page.&lt;/p&gt;

&lt;p&gt;The third is optimizing once and then reusing that compressed file as the source for the next channel. A marketplace listing, an Instagram post, and your store should all come from the original shoot, not from each other. Every generation costs quality, and the cost is invisible until a customer zooms in.&lt;/p&gt;

&lt;p&gt;Pick your bestselling product and run its photos through the checklist today: one product, one preset pass, one DevTools check. If the collection page feels faster on your phone afterward, work through the rest of the catalog in batches. The &lt;a href="https://getsnapshrink.com/presets/shopify-image-optimizer/" rel="noopener noreferrer"&gt;Shopify image optimizer preset&lt;/a&gt; keeps the settings consistent across the whole catalog, so the tenth product gets the same treatment as the first.&lt;/p&gt;

</description>
      <category>shopify</category>
      <category>webdev</category>
      <category>webperf</category>
      <category>ecommerce</category>
    </item>
    <item>
      <title>Image Optimization for Core Web Vitals: Fix Your LCP</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Sat, 24 Oct 2026 04:26:08 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/image-optimization-for-core-web-vitals-fix-your-lcp-4mlp</link>
      <guid>https://dev.to/nawalshrestha/image-optimization-for-core-web-vitals-fix-your-lcp-4mlp</guid>
      <description>&lt;h1&gt;
  
  
  Image Optimization for Core Web Vitals: Fix Your LCP
&lt;/h1&gt;

&lt;p&gt;You run Lighthouse on the homepage. The score lands at 47, painted in angry red. Largest Contentful Paint sits at 5.8 seconds, and when you dig into the trace, the culprit is embarrassing: a 2.1MB hero JPEG, served at full desktop resolution to a phone.&lt;/p&gt;

&lt;p&gt;Welcome to image optimization core web vitals work: the unglamorous, high-leverage job of making your pictures weigh less. LCP is the most image-driven of the three Core Web Vitals, and images are almost always the heaviest thing on the page.&lt;/p&gt;

&lt;p&gt;Unlike most Core Web Vitals guides, this one gives you concrete KB budgets per image type and a worked audit you can repeat in DevTools. I build SnapShrink, a 100%-in-browser image compressor, so shrinking pictures is quite literally my day job.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why LCP is usually an image problem
&lt;/h2&gt;

&lt;p&gt;LCP measures when the largest visible element on screen finishes rendering, and on most pages that element is an image: a hero banner, a product photo, a featured post image. Text and CSS arrive in milliseconds, while a 2MB picture takes seconds on a mobile connection. Since Google wants LCP &lt;a href="https://developers.google.com/search/docs/appearance/core-web-vitals" rel="noopener noreferrer"&gt;under 2.5 seconds&lt;/a&gt;, image weight is usually the whole battle.&lt;/p&gt;

&lt;p&gt;Here is the math that makes it obvious. The HTML, CSS, and fonts on a typical marketing page weigh 100 to 300KB combined. One unoptimized hero image can weigh ten times that. The LCP element has to download, decode, and paint before the metric stops, so every extra megabyte stretches the timeline on a real mobile connection. Shrink the image and the metric usually follows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Find your LCP image in under two minutes
&lt;/h2&gt;

&lt;p&gt;Open Chrome DevTools, run Lighthouse from the Performance panel, and open the generated report. Scroll to the LCP element in the diagnostics section and click it; DevTools highlights the exact image on your page and shows its size and format. Note the file weight and the rendered dimensions, because the gap between the two is where your savings live.&lt;/p&gt;

&lt;p&gt;The routine, step by step:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Run Lighthouse on the page with mobile emulation on. The default settings are fine; you want the same conditions Google scores.&lt;/li&gt;
&lt;li&gt;In the report, find "Largest Contentful Paint element" under Diagnostics and click it. DevTools jumps straight to the image in the Elements panel.&lt;/li&gt;
&lt;li&gt;Compare natural and rendered dimensions. If the file is 2400 pixels wide but renders at 390, you are shipping six times the pixels anyone sees.&lt;/li&gt;
&lt;li&gt;Cross-check in the Network tab: filter by Img, sort by Size, reload with the cache disabled. The heaviest files float to the top, and the LCP image is usually one of the first three rows.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Set a KB budget before you touch a codec
&lt;/h2&gt;

&lt;p&gt;Every image optimization core web vitals project I have run started with a budget, not a compressor. Decide the file size each image type is allowed before you touch anything: hero images get 150KB on desktop, 80KB on mobile; thumbnails get 30KB; avatars and icons get 15KB or ship as SVG. A budget turns optimization into a number you can verify.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Image type&lt;/th&gt;
&lt;th&gt;Desktop budget&lt;/th&gt;
&lt;th&gt;Mobile budget&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Hero / banner&lt;/td&gt;
&lt;td&gt;150KB&lt;/td&gt;
&lt;td&gt;80KB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Product / feature shots&lt;/td&gt;
&lt;td&gt;100KB&lt;/td&gt;
&lt;td&gt;60KB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Card thumbnails&lt;/td&gt;
&lt;td&gt;30KB&lt;/td&gt;
&lt;td&gt;30KB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Avatars / icons&lt;/td&gt;
&lt;td&gt;15KB (or SVG)&lt;/td&gt;
&lt;td&gt;15KB (or SVG)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are the ceilings I start from. They assume photographic content saved as WebP at quality 75 to 85. Illustrations and screenshots with flat colors compress far better, so treat the numbers as ceilings to stay under. If you like working backwards from the number, you can &lt;a href="https://getsnapshrink.com/compress-image-to-100kb/" rel="noopener noreferrer"&gt;compress an image to an exact KB target&lt;/a&gt; in the browser instead of guessing at quality sliders.&lt;/p&gt;

&lt;h2&gt;
  
  
  The re-encode walkthrough: 2.1MB to about 110KB
&lt;/h2&gt;

&lt;p&gt;Take the 2.1MB hero from our Lighthouse trace: a 2400x1600 JPEG served to every device. Resize it to the largest width the layout actually renders, 1600 pixels here, re-encode it to WebP at quality 80, and the file drops to roughly 100 to 140KB with no visible difference on screen. That single change typically cuts LCP by two to four seconds on a mobile connection.&lt;/p&gt;

&lt;p&gt;The loop, in order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Resize to the rendered width first. If the layout never shows the hero wider than 1600 pixels, a 2400-pixel source is pure wasted bytes. Resizing is the cheapest win in the whole process.&lt;/li&gt;
&lt;li&gt;Pick WebP as your default. For photographic content it typically cuts 25 to 35 percent off an equivalent-quality JPEG. Keep the JPEG only if you still support truly ancient browsers; everything modern renders WebP.&lt;/li&gt;
&lt;li&gt;Set quality between 75 and 85. Below 75, banding creeps into skies and gradients. Above 85, the file size climbs fast for differences nobody can see. I default to 80 and adjust by eye.&lt;/li&gt;
&lt;li&gt;Compare the result against the original at 100 percent zoom. If you cannot spot the difference on a careful look, your users will not spot it at all. Ship it.&lt;/li&gt;
&lt;li&gt;Re-run Lighthouse. The LCP number should move a lot. If it barely budges, the LCP element was not the file you optimized, and the audit in the second section sent you to the wrong image.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I built &lt;a href="https://getsnapshrink.com/compress-image/" rel="noopener noreferrer"&gt;SnapShrink's free browser-based image compressor&lt;/a&gt; for exactly this loop: drop in the hero, resize, pick WebP, and everything re-encodes on your machine with nothing uploaded.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your image optimization core web vitals questions, answered
&lt;/h2&gt;

&lt;p&gt;Three questions come up every time image optimization core web vitals work lands on a developer's desk: whether lazy loading fixes LCP, whether AVIF is worth the hassle, and whether compression or responsive images matter more. Here are the short answers, with the tradeoffs that change the decision in practice.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will lazy-loading the hero fix my LCP?
&lt;/h3&gt;

&lt;p&gt;No. It usually makes LCP worse. &lt;a href="https://web.dev/articles/browser-level-image-lazy-loading" rel="noopener noreferrer"&gt;Lazy loading&lt;/a&gt; defers offscreen images, but the LCP image is on screen by definition, so you would be adding delay to the exact thing you are trying to speed up. Mark the LCP image with fetchpriority="high", consider a preload link for it, and lazy-load everything below the fold. Google's guide to &lt;a href="https://web.dev/articles/optimize-lcp" rel="noopener noreferrer"&gt;optimizing LCP&lt;/a&gt; walks through prioritizing the LCP element in detail.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is AVIF worth switching to?
&lt;/h3&gt;

&lt;p&gt;Not as your first move. AVIF typically shaves another 15 to 25 percent off WebP at matched visual quality, but encoding is slower and the tooling is thinner. Nail WebP first; add AVIF later.&lt;/p&gt;

&lt;h3&gt;
  
  
  Compression or responsive images: which first?
&lt;/h3&gt;

&lt;p&gt;Compression first, responsive images second. Re-encoding one hero from JPEG to WebP can remove 70 to 90 percent of its weight in ten minutes. Responsive images with srcset and sizes stop you shipping desktop pixels to phones, which matters, but it is a code change across templates. Do the quick win this afternoon; schedule the srcset work for the sprint.&lt;/p&gt;

&lt;p&gt;Back to that homepage scoring 47. Find the LCP image, give it a KB budget, re-encode it, and run Lighthouse again. LCP should drop hard, and the score usually follows it into the green. One page, one image, one afternoon.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>performance</category>
      <category>webperf</category>
      <category>seo</category>
    </item>
    <item>
      <title>WebP vs PNG vs JPEG: Which Format Should You Serve in 2026?</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Wed, 21 Oct 2026 04:38:16 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/webp-vs-png-vs-jpeg-which-format-should-you-serve-in-2026-207c</link>
      <guid>https://dev.to/nawalshrestha/webp-vs-png-vs-jpeg-which-format-should-you-serve-in-2026-207c</guid>
      <description>&lt;h1&gt;
  
  
  WebP vs PNG vs JPEG: Which Format Should You Serve in 2026?
&lt;/h1&gt;

&lt;p&gt;Last week I ran SnapShrink's batch converter over a folder of 200 demo images for the tool's gallery. One PNG screenshot went in at 412 KB and came out at 96 KB as WebP. Same pixels, no visible difference. That folder is why I stopped treating webp vs png as a taste question. It's arithmetic now. Here's how I decide what to serve.&lt;/p&gt;

&lt;h2&gt;
  
  
  WebP vs PNG: how much smaller is WebP, really?
&lt;/h2&gt;

&lt;p&gt;WebP is consistently smaller than PNG. Google's published WebP study measured lossless WebP at roughly 26% smaller than equivalent PNG files, and lossy WebP at 25 to 34% smaller than JPEG at comparable visual quality. Savings vary by image, but for anything served on a website, WebP almost always wins on size.&lt;/p&gt;

&lt;p&gt;The catch is that WebP has two modes and they behave very differently. Lossy WebP is what you want for photos. Lossless WebP is what you want for screenshots, logos, and anything with text or hard edges. Mixing them up is the most common mistake I see. Lossy on a screenshot smears the text; lossless on a photo wastes bytes for detail your eyes can't see.&lt;/p&gt;

&lt;p&gt;One honest caveat from building a converter: for very tiny or simple images, WebP's container overhead can wipe out the compression gain, and I've seen small icons where PNG came out ahead. Spot-check your own assets instead of trusting a rule.&lt;/p&gt;

&lt;h2&gt;
  
  
  WebP vs PNG for transparency and animation
&lt;/h2&gt;

&lt;p&gt;WebP supports 8-bit alpha transparency and animation, so it covers every job PNG does except one: legacy compatibility. PNG still wins when the destination app only reads PNG, like some email clients, design tools, and old CMS pipelines. For animation, WebP beats GIF on file size, but actual video formats beat both WebP and GIF by a wide margin.&lt;/p&gt;

&lt;p&gt;Transparency is the feature that made me stop defaulting to PNG. Early WebP had a reputation for rough alpha edges, but modern encoders handle it fine, and the files are much smaller. The one failure mode I watch for: converting a PNG with semi-transparent pixels and not checking the result. Alpha is the one thing that can break silently, so I always eyeball the converted file against a dark background.&lt;/p&gt;

&lt;p&gt;For animation, WebP is technically fine and far smaller than GIF, but the authoring and tooling ecosystem never caught up. Short looping clips belong in muted MP4 or WebM. They compress better than any image format and browsers play them natively.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where JPEG still beats both
&lt;/h2&gt;

&lt;p&gt;JPEG wins on universal compatibility and encoding speed, not quality per byte. Every device built in the last twenty years reads JPEG, and encoding is instant. For photos served to old email clients, RSS readers, or user-uploaded avatars you don't control, JPEG at 80 to 85 quality remains the safe pick.&lt;/p&gt;

&lt;p&gt;JPEG also has no alpha channel and no lossless mode, so don't force it into jobs it can't do. Text screenshots saved as JPEG get that familiar smudged look around every letter, which is why it's the wrong tool for UI images. Use it for photos aimed at destinations you can't control, and use WebP or PNG for everything else.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 2026 decision framework I actually use
&lt;/h2&gt;

&lt;p&gt;My rule is deliberately boring: photos and screenshots go to WebP, lossy for photos and lossless for anything with text or hard edges, with PNG reserved for tools that force it and JPEG for photos aimed at destinations I can't control. Everything gets wrapped in a picture element so the browser picks the best format it understands.&lt;/p&gt;

&lt;p&gt;The picture element does the heavy lifting, so your markup doesn't have to guess:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;picture&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;source&lt;/span&gt; &lt;span class="na"&gt;srcset=&lt;/span&gt;&lt;span class="s"&gt;"hero.avif"&lt;/span&gt; &lt;span class="na"&gt;type=&lt;/span&gt;&lt;span class="s"&gt;"image/avif"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;source&lt;/span&gt; &lt;span class="na"&gt;srcset=&lt;/span&gt;&lt;span class="s"&gt;"hero.webp"&lt;/span&gt; &lt;span class="na"&gt;type=&lt;/span&gt;&lt;span class="s"&gt;"image/webp"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;img&lt;/span&gt; &lt;span class="na"&gt;src=&lt;/span&gt;&lt;span class="s"&gt;"hero.jpg"&lt;/span&gt; &lt;span class="na"&gt;alt=&lt;/span&gt;&lt;span class="s"&gt;"Product dashboard screenshot"&lt;/span&gt; &lt;span class="na"&gt;width=&lt;/span&gt;&lt;span class="s"&gt;"1200"&lt;/span&gt; &lt;span class="na"&gt;height=&lt;/span&gt;&lt;span class="s"&gt;"630"&lt;/span&gt; &lt;span class="na"&gt;loading=&lt;/span&gt;&lt;span class="s"&gt;"lazy"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/picture&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Browsers read the sources top to bottom and take the first format they support. Old browsers fall through to the JPEG. You can add AVIF at the top of the stack later without touching anything else, which is exactly how I future-proofed the SnapShrink gallery.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;Serve this&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Photo on a modern site&lt;/td&gt;
&lt;td&gt;WebP lossy, ~75-82 quality&lt;/td&gt;
&lt;td&gt;Smallest file at good quality&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Screenshot, logo, UI with text&lt;/td&gt;
&lt;td&gt;WebP lossless&lt;/td&gt;
&lt;td&gt;Sharp edges, alpha support, far smaller than PNG&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Destination only accepts PNG&lt;/td&gt;
&lt;td&gt;PNG&lt;/td&gt;
&lt;td&gt;Compatibility beats bytes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Photo for email, RSS, unknown clients&lt;/td&gt;
&lt;td&gt;JPEG, 80-85 quality&lt;/td&gt;
&lt;td&gt;Universal support, instant encode&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Short looping animation&lt;/td&gt;
&lt;td&gt;Muted MP4/WebM&lt;/td&gt;
&lt;td&gt;Beats every image format on size&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Simple icon&lt;/td&gt;
&lt;td&gt;SVG, or PNG if raster&lt;/td&gt;
&lt;td&gt;Vector scales; PNG is the safe raster&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How to convert without breaking things
&lt;/h2&gt;

&lt;p&gt;Convert originals to WebP at build or upload time, never by hand-editing files on a live server. Keep your PNG masters archived for anything an external tool might need later, and always check alpha channels after conversion, since a broken alpha channel fails silently and looks terrible on dark backgrounds.&lt;/p&gt;

&lt;p&gt;If you want the full file-size numbers and the technical background in one place, I've written a deeper &lt;a href="https://getsnapshrink.com/blog/webp-vs-png/" rel="noopener noreferrer"&gt;WebP vs PNG comparison on the SnapShrink blog&lt;/a&gt;. And for the reverse trip, when some tool insists on a PNG, SnapShrink's &lt;a href="https://getsnapshrink.com/webp-to-png/" rel="noopener noreferrer"&gt;free WebP to PNG converter&lt;/a&gt; handles the conversion in your browser with no upload.&lt;/p&gt;

&lt;p&gt;Two practical gotchas before you convert a whole library. First, social and chat link previews still prefer JPEG or PNG for og:image, so don't WebP your share images. Second, WebP doesn't magically fix a bad source: a blurry JPEG converted to WebP is a small blurry image. Start from the highest-quality original you have.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;The short version of everything above: serve WebP by default, keep PNG for compatibility, use JPEG for photos aimed at old clients, and try AVIF behind WebP in your picture element if you feel like experimenting. The questions below cover the edge cases I get asked most.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is WebP always smaller than PNG?
&lt;/h3&gt;

&lt;p&gt;No. For most web images, yes, and usually by a lot. But for very small or very simple images, WebP's container overhead can eat the gain, and PNG sometimes comes out ahead. Test your own assets instead of trusting a blanket rule.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I convert my entire PNG library to WebP?
&lt;/h3&gt;

&lt;p&gt;Only the files you actually serve on the web. Keep PNG masters archived. Re-converting from a lossy WebP back to PNG later is a one-way trip you don't want to take.&lt;/p&gt;

&lt;h3&gt;
  
  
  What about AVIF?
&lt;/h3&gt;

&lt;p&gt;AVIF typically compresses 20 to 30% smaller than WebP's lossy mode, but encoding is noticeably slower and tooling support is still catching up. It's worth trying behind a picture element where WebP is the fallback. Don't rebuild your whole pipeline around it yet.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does WebP work in every browser?
&lt;/h3&gt;

&lt;p&gt;All modern browsers have supported WebP since around 2020, including Safari from version 14. The picture element pattern above covers the stragglers with a JPEG fallback, so browser support shouldn't stop you.&lt;/p&gt;

&lt;p&gt;Remember that 412 KB screenshot from the demo folder? It shipped as a 96 KB WebP and nobody noticed except me, checking the network tab. That's the whole pitch. Pick WebP as your default, keep PNG and JPEG for the jobs they still own, and let the picture element sort out the rest. Your users' bandwidth will thank you.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>webperf</category>
      <category>images</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>JFIF to JPG, WebP to GIF, HEIC to PNG Explained</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Sat, 17 Oct 2026 04:26:34 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/jfif-to-jpg-webp-to-gif-heic-to-png-explained-4if8</link>
      <guid>https://dev.to/nawalshrestha/jfif-to-jpg-webp-to-gif-heic-to-png-explained-4if8</guid>
      <description>&lt;h1&gt;
  
  
  JFIF to JPG, WebP to GIF, HEIC to PNG: Three Conversions That Confuse Everyone
&lt;/h1&gt;

&lt;p&gt;You hit Save, and instead of photo.jpg you get photo.jfif. The upload form rejects it. You stare at the extension like it personally wronged you.&lt;/p&gt;

&lt;p&gt;I build SnapShrink, a browser-based image tool, so I collect these moments. That .jfif confusion is one of three format conversions that trip up basically everyone. The other two: a WebP animation the platform won't accept, and iPhone photos that won't open on Windows. Here's what each one actually is, and the fastest way through it.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. JFIF to JPG: the format you've used without knowing
&lt;/h2&gt;

&lt;p&gt;If you've ever saved an image and gotten a &lt;code&gt;.jfif&lt;/code&gt; file instead of &lt;code&gt;.jpg&lt;/code&gt;, you've met JFIF. Despite the unfamiliar extension, it's a JPEG under the hood — JFIF (JPEG File Interchange Format) is just a slightly different container for the same data. Your camera, your phone, and half the software on your computer treat them as the same thing.&lt;/p&gt;

&lt;p&gt;The problem is the other half. Some upload forms, older editors, and picky CMS platforms reject &lt;code&gt;.jfif&lt;/code&gt; outright because the extension isn't on their allowlist. The file is fine; the extension is the problem.&lt;/p&gt;

&lt;p&gt;The fix takes seconds: converting JFIF to JPG just rewrites the container, no recompression, no quality loss. I run a &lt;a href="https://getsnapshrink.com/jfif-to-jpg/" rel="noopener noreferrer"&gt;free JFIF to JPG converter&lt;/a&gt; for exactly this — drop the file in, get a &lt;code&gt;.jpg&lt;/code&gt; back, upload wherever you were blocked.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. WebP to GIF: when you need the animation, not the efficiency
&lt;/h2&gt;

&lt;p&gt;WebP is the better format on paper. Smaller files than JPEG, supports transparency like PNG, and handles animation too. Google's been pushing it for a decade and browsers finally all support it.&lt;/p&gt;

&lt;p&gt;But "better on paper" doesn't matter when the tool on the other end doesn't accept it. Email clients, some chat apps, forum software from 2015, design tools with frozen feature sets — plenty of places still only speak GIF for animations. I hit this making demo clips: record as WebP, then discover the platform I'm posting to wants GIF.&lt;/p&gt;

&lt;p&gt;Converting WebP to GIF re-encodes the animation frames. Quality takes a small hit (GIF is limited to 256 colors per frame), so keep the source WebP archived. For the actual conversion I use an &lt;a href="https://getsnapshrink.com/webp-to-gif/" rel="noopener noreferrer"&gt;in-browser WebP to GIF tool&lt;/a&gt; — nothing uploads anywhere, which matters when the clip is client work.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. HEIC to PNG: iPhone photos on a Windows machine
&lt;/h2&gt;

&lt;p&gt;This is the one that generates the most confused messages. You AirDrop or transfer photos from an iPhone to a Windows PC, and half of them won't open. Those are HEIC files — Apple's default photo format since iOS 11. It's genuinely good tech (about half the file size of JPEG at the same quality), but Windows support is still patchy in 2026.&lt;/p&gt;

&lt;p&gt;PNG is the safe target here, not JPG. If you're pulling photos off a phone to edit or archive, PNG keeps every pixel — no generational loss on top of whatever the phone already did. JPG is fine for sharing; PNG is right for keeping.&lt;/p&gt;

&lt;p&gt;The conversion is straightforward with a &lt;a href="https://getsnapshrink.com/heic-to-png/" rel="noopener noreferrer"&gt;HEIC to PNG converter&lt;/a&gt;. One thing to watch: HEIC files sometimes contain multiple images (bursts, live photo frames). A decent converter handles the primary image; if you need every frame of a burst, that's a separate job.&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on where the conversion happens
&lt;/h2&gt;

&lt;p&gt;All three tools I linked above run entirely in your browser. Most people never check this: the majority of "free online converters" upload your file to a server, convert it there, and hand it back. For a meme, who cares. For client photos, unreleased product shots, or anything with people in it, that upload is a privacy decision you're making without realizing it.&lt;/p&gt;

&lt;p&gt;You can verify the browser-only claim yourself in about ten seconds: open DevTools, go to the Network tab, run a conversion. If the network stays quiet, the file never left your machine. I built SnapShrink this way because I got tired of wondering where my files went.&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;JFIF → JPG&lt;/strong&gt;: same image, friendlier extension. Container swap, zero quality loss.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WebP → GIF&lt;/strong&gt;: for the platforms stuck in 2015. Real re-encode, keep your source.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;HEIC → PNG&lt;/strong&gt;: iPhone photos on Windows. PNG for archiving, JPG for sharing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check where conversion happens&lt;/strong&gt; before uploading anything you wouldn't post publicly.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Three conversions, three tools, no accounts, no uploads. And next time a save dialog hands you a .jfif, you'll know exactly what it is — and exactly where to take it.&lt;/p&gt;

</description>
      <category>image</category>
      <category>webdev</category>
      <category>tutorial</category>
      <category>beginners</category>
    </item>
    <item>
      <title>I compared TinyPNG alternatives on privacy, not just file size</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Wed, 07 Oct 2026 16:15:41 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/i-compared-tinypng-alternatives-on-privacy-not-just-file-size-1l6j</link>
      <guid>https://dev.to/nawalshrestha/i-compared-tinypng-alternatives-on-privacy-not-just-file-size-1l6j</guid>
      <description>&lt;p&gt;Everyone's used TinyPNG. It's the default "make this image smaller" tool, and its compression is genuinely good. But every roundup I read compares these tools on file size alone, and in 2026 that's the least interesting difference between them.&lt;/p&gt;

&lt;p&gt;Here's the direct answer: the tools differ less on file size than on where your images get processed and what you pay. TinyPNG uploads your files to its servers and charges a subscription (Web Pro is $3.25/month billed annually — $39/year, verified on their pricing page today). Browser-local tools like Squoosh and SnapShrink process everything on your device. I build &lt;a href="https://getsnapshrink.com/" rel="noopener noreferrer"&gt;SnapShrink&lt;/a&gt;, a batch image compressor that runs 100% in the browser, and I'll tell you exactly where TinyPNG still wins. If you handle client photos, ID scans, or unreleased work, the privacy angle matters more than a 5% size difference, and almost nobody writes about it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4j193sfjktrji7f2dgcz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4j193sfjktrji7f2dgcz.png" alt="SnapShrink's batch compressor running entirely in the browser — drop images, no upload" width="800" height="416"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The comparison that actually matters
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;TinyPNG&lt;/th&gt;
&lt;th&gt;Squoosh&lt;/th&gt;
&lt;th&gt;SnapShrink&lt;/th&gt;
&lt;th&gt;Compressor.io&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Where files are processed&lt;/td&gt;
&lt;td&gt;Their servers&lt;/td&gt;
&lt;td&gt;Your browser&lt;/td&gt;
&lt;td&gt;Your browser&lt;/td&gt;
&lt;td&gt;Their servers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Free batch limit&lt;/td&gt;
&lt;td&gt;20 images, 5 MB each&lt;/td&gt;
&lt;td&gt;1 image at a time&lt;/td&gt;
&lt;td&gt;10/session, no file cap&lt;/td&gt;
&lt;td&gt;~10/session&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pricing&lt;/td&gt;
&lt;td&gt;Free tier + Pro/Ultra subscriptions ($39/year Pro)&lt;/td&gt;
&lt;td&gt;Free forever&lt;/td&gt;
&lt;td&gt;$9 one-time&lt;/td&gt;
&lt;td&gt;Free tier + subscription&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;API / WordPress plugin&lt;/td&gt;
&lt;td&gt;Yes, mature&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Target an exact file size&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes (type the KB)&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;EXIF stripped&lt;/td&gt;
&lt;td&gt;Server-side&lt;/td&gt;
&lt;td&gt;N/A (local)&lt;/td&gt;
&lt;td&gt;On-device, automatic&lt;/td&gt;
&lt;td&gt;Server-side&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;TinyPNG's free tier is honest: 20 images at once, 5 MB each. The paid product is a subscription — $39/year for Web Pro, $149/year for Ultra. That's a fine model for a server-side tool, because bandwidth and compute cost real money per image. It's just worth asking whether &lt;em&gt;your&lt;/em&gt; use case needs a server at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  How does in-browser compression actually work?
&lt;/h2&gt;

&lt;p&gt;No magic, and no server: the browser reads your files with the File API, encodes them in a Web Worker (so the tab stays responsive), and hands you the bytes back. The network is never involved — your CPU does the work your laptop was already going to do.&lt;/p&gt;

&lt;p&gt;The quality difference people worry about is real but small. Browser canvas encoders are a bit less efficient than TinyPNG's proprietary quantizer at maximum compression, but encoder choice matters less than &lt;em&gt;your&lt;/em&gt; settings. On a 3000×2000 test photo I measured, JPEG quality 80 came out ~42% smaller than quality 95 with no visible difference at normal viewing distance — and switching the same photo to &lt;a href="https://getsnapshrink.com/webp-converter/" rel="noopener noreferrer"&gt;WebP&lt;/a&gt; at quality 80 cut the file to less than half the JPEG. Quality level, dimensions, and format dwarf the tool-to-tool gap.&lt;/p&gt;

&lt;h2&gt;
  
  
  How can you verify a compressor really keeps your files local?
&lt;/h2&gt;

&lt;p&gt;Don't trust privacy policies — test them. This 30-second check works on every compressor on the market, including mine:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open any compressor, press F12 → Network tab.&lt;/li&gt;
&lt;li&gt;Drop in photos, compress.&lt;/li&gt;
&lt;li&gt;Filter for uploads (POST/PUT with file bodies).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;With a browser-local tool you'll see zero — because there are none to see. Run the same test on a server-side compressor and watch the difference.&lt;/p&gt;

&lt;p&gt;There's a second angle nobody mentions: EXIF data. Phone photos carry GPS coordinates, timestamps, device info. Upload that to a server compressor and the metadata travels with the file — you're trusting their pipeline to strip it. Local tools strip it on your device before anything could leave. (I wrote up &lt;a href="https://getsnapshrink.com/blog/strip-metadata-from-photos/" rel="noopener noreferrer"&gt;why that matters&lt;/a&gt; separately.)&lt;/p&gt;

&lt;h2&gt;
  
  
  When should you stick with TinyPNG?
&lt;/h2&gt;

&lt;p&gt;Plenty of cases where I'd pick TinyPNG myself:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You need compression inside an automated workflow — build pipeline, CMS, upload endpoint. TinyPNG's API is built for exactly that; browser tools are manual.&lt;/li&gt;
&lt;li&gt;You use the WordPress plugin. Mature, set-and-forget.&lt;/li&gt;
&lt;li&gt;You want their specific PNG quantization. For aggressive PNG size reduction it's still excellent.&lt;/li&gt;
&lt;li&gt;You're compressing 1–5 images occasionally and don't care about uploads or subscriptions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The honest version: these tools overlap but aren't identical. TinyPNG has the ecosystem. Browser-local tools have the privacy model and (in our case) the pricing model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why can a browser tool charge $9 once while TinyPNG charges $39/year?
&lt;/h2&gt;

&lt;p&gt;Because the cost structures are completely different. Server-side tools pay for bandwidth and compute on every single image — subscriptions make sense for them. A browser tool's marginal cost per image is ~zero after the page loads, so charging monthly rent for it is a business choice, not a technical necessity.&lt;/p&gt;

&lt;p&gt;That's the whole argument for $9 once: pay through Dodo Payments, get a license key by email, paste it in, done. Offline verification, no account, 14-day money-back guarantee.&lt;/p&gt;

&lt;p&gt;Limitations, stated plainly: no API, no WordPress plugin, no AVIF output in v1, 10 free images per session. If any of those are your workflow, TinyPNG or Squoosh is the better pick.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Is SnapShrink actually free?
&lt;/h3&gt;

&lt;p&gt;The first 10 images per session are free, no account needed. After that it's a $9 one-time payment for unlimited use — not a subscription. There's a 14-day money-back guarantee, and the license is verified offline, so the tool keeps working even without an account system.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does browser compression match TinyPNG's quality?
&lt;/h3&gt;

&lt;p&gt;Close enough that your settings matter more than your tool. TinyPNG's quantizer has a small edge on maximum PNG compression, but quality level, dimensions, and format choice (especially WebP) move file size far more than encoder choice. My own test: JPEG quality 80 vs 95 on the same photo — 42% smaller, no visible difference.&lt;/p&gt;

&lt;h3&gt;
  
  
  What happens to EXIF data in my photos?
&lt;/h3&gt;

&lt;p&gt;It's stripped on your device, automatically, before anything could leave — because nothing ever leaves. With server-side compressors, your GPS coordinates and timestamps travel with the upload and you're trusting their pipeline to strip them. I wrote a &lt;a href="https://getsnapshrink.com/blog/strip-metadata-from-photos/" rel="noopener noreferrer"&gt;separate guide on stripping metadata from photos&lt;/a&gt; if you want the full picture.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I hit an exact file size, like under 100KB?
&lt;/h3&gt;

&lt;p&gt;Yes — that's the one thing most compressors can't do. Instead of guessing the quality slider, you &lt;a href="https://getsnapshrink.com/compress-image-to-exact-kb/" rel="noopener noreferrer"&gt;compress an image to an exact file size&lt;/a&gt; by typing the target KB, and the tool finds the quality setting that fits at or under it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnswnxrhu9bwuqzt5hiia.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnswnxrhu9bwuqzt5hiia.png" alt="Type a target KB value and the tool finds the quality setting that fits under it" width="800" height="416"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;The longer version with the full comparison table and decision matrix lives on the blog: &lt;a href="https://getsnapshrink.com/blog/tinypng-alternative-pay-once/" rel="noopener noreferrer"&gt;TinyPNG Alternative You Pay Once ($9)&lt;/a&gt;. Try the tool free — &lt;a href="https://getsnapshrink.com/app/" rel="noopener noreferrer"&gt;getsnapshrink.com/app&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webperf</category>
      <category>privacy</category>
      <category>webdev</category>
      <category>images</category>
    </item>
    <item>
      <title>Stop Guessing the Quality Slider — Binary-Searching JPEG Quality for Exact File Sizes</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Tue, 06 Oct 2026 12:19:43 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/stop-guessing-the-quality-slider-binary-searching-jpeg-quality-for-exact-file-sizes-4g53</link>
      <guid>https://dev.to/nawalshrestha/stop-guessing-the-quality-slider-binary-searching-jpeg-quality-for-exact-file-sizes-4g53</guid>
      <description>&lt;p&gt;Here's a UX problem every image tool punts on: the user doesn't want "quality 80". They want "under 100KB" — because a form said so. The quality slider is the tool's internal machinery exposed as UI. Users shouldn't have to learn your encoder's quality curve.&lt;/p&gt;

&lt;p&gt;In &lt;a href="https://getsnapshrink.com/compress-image-to-exact-kb/" rel="noopener noreferrer"&gt;SnapShrink&lt;/a&gt; I built Target KB mode: type &lt;code&gt;20&lt;/code&gt;, get a file at or under 20KB. Here's the approach.&lt;/p&gt;

&lt;h2&gt;
  
  
  The algorithm
&lt;/h2&gt;

&lt;p&gt;It's a binary search over the quality parameter:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Set bounds: quality 1–100 (or your encoder's range).&lt;/li&gt;
&lt;li&gt;Encode at mid quality, measure the output bytes.&lt;/li&gt;
&lt;li&gt;If over target, search the lower half; if under, search the upper half — keeping the best valid result.&lt;/li&gt;
&lt;li&gt;~7 iterations converges. Each iteration is a fast in-memory encode; no network involved.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The key detail: &lt;strong&gt;quality is searched first, dimensions last.&lt;/strong&gt; Only if quality=1 still overshoots do you downscale slightly and re-run the search. Most photos hit common caps (20/50/100KB) with dimensions untouched, which is what users expect — they asked for a size, not a resize.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters more than it sounds
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Government and exam portals (India's UPSC forms: 20–300KB caps) reject oversized uploads with zero guidance. "Type the number" beats a slider every time.&lt;/li&gt;
&lt;li&gt;It composes with batch: set the target once, every file in the batch gets its own binary search, download as ZIP.&lt;/li&gt;
&lt;li&gt;It works client-side. The encodes are cheap enough to run in a Web Worker without blocking the page.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The honest edge cases
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Tiny targets on huge photos will visibly degrade — that's physics, not a bug. Showing the achieved size when the target is unreachable beats silently overshooting.&lt;/li&gt;
&lt;li&gt;PNGs with sharp text compress differently than photos; the search handles both because it measures actual bytes, not estimates.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you maintain an image tool, consider exposing the target instead of (or alongside) the slider. Users think in file sizes. Meet them there.&lt;/p&gt;

&lt;p&gt;Live at &lt;a href="https://getsnapshrink.com/compress-image-to-exact-kb/" rel="noopener noreferrer"&gt;getsnapshrink.com/compress-image-to-exact-kb/&lt;/a&gt; — first 10 images per session free, everything runs in the browser. The same engine also powers &lt;a href="https://getsnapshrink.com/heic-to-jpg/" rel="noopener noreferrer"&gt;HEIC→JPG&lt;/a&gt; and &lt;a href="https://getsnapshrink.com/avif-to-jpg/" rel="noopener noreferrer"&gt;AVIF→JPG&lt;/a&gt; conversion — new input formats turned out to be just a decode step.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>images</category>
      <category>algorithms</category>
    </item>
    <item>
      <title>I Added Client-Side HEIC to JPG Conversion to My Image Tool — No Server, No Upload</title>
      <dc:creator>Nawal Shrestha</dc:creator>
      <pubDate>Tue, 06 Oct 2026 12:18:07 +0000</pubDate>
      <link>https://dev.to/nawalshrestha/i-added-client-side-heic-to-jpg-conversion-to-my-image-tool-no-server-no-upload-46oh</link>
      <guid>https://dev.to/nawalshrestha/i-added-client-side-heic-to-jpg-conversion-to-my-image-tool-no-server-no-upload-46oh</guid>
      <description>&lt;p&gt;Most "free HEIC to JPG" tools work the same way: you upload your iPhone photos to someone's server, it converts them, you download the result. For a format conversion — one of the most local operations imaginable — that's a strange trade.&lt;/p&gt;

&lt;p&gt;I wanted HEIC to JPG support in &lt;a href="https://getsnapshrink.com/heic-to-jpg/" rel="noopener noreferrer"&gt;SnapShrink&lt;/a&gt; (my in-browser batch image compressor) without breaking its core promise: nothing ever uploads. Here's how I did it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The decoder: heic2any, lazy-loaded
&lt;/h2&gt;

&lt;p&gt;Browsers can't decode HEIC natively (unlike AVIF, which Chrome/Edge/Firefox handle via &lt;code&gt;createImageBitmap&lt;/code&gt;). So the conversion needs a real decoder. I used &lt;a href="https://github.com/alexcorvi/heic2any" rel="noopener noreferrer"&gt;heic2any&lt;/a&gt;, pinned to a fixed version, loaded via dynamic &lt;code&gt;import()&lt;/code&gt; &lt;strong&gt;only when a HEIC file is actually dropped&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;That last part matters: the decoder is a chunk of WASM/JS you don't want in the initial bundle for the 95% of users who never touch HEIC. Lazy-loading keeps the first paint fast for everyone.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pipeline
&lt;/h2&gt;

&lt;p&gt;Once decoded, a HEIC file is just pixels — it flows into the exact same pipeline as every other format:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Decode → ImageData/canvas&lt;/li&gt;
&lt;li&gt;Quality slider or Target KB mode (binary-search the quality setting until the output fits)&lt;/li&gt;
&lt;li&gt;Encode to JPG/PNG/WebP, batch, ZIP download&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;No HEIC-specific special cases downstream. That was the whole point of the architecture: new input formats are a decode step, not a new app. AVIF support later followed the same path — &lt;a href="https://getsnapshrink.com/avif-to-jpg/" rel="noopener noreferrer"&gt;same idea, native decode&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The UX details that matter
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Files get a small "HEIC" badge in the drop list so users can see what was detected.&lt;/li&gt;
&lt;li&gt;A misnamed file (&lt;code&gt;.heic&lt;/code&gt; that's actually a JPEG) gets a clear error instead of a cryptic decoder failure.&lt;/li&gt;
&lt;li&gt;Target KB mode works on HEIC too — type &lt;code&gt;100&lt;/code&gt;, get ≤100KB. This is the feature people actually write in about: forms with hard size caps. (&lt;a href="https://getsnapshrink.com/compress-image-to-exact-kb/" rel="noopener noreferrer"&gt;How it works&lt;/a&gt;.)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Drop a real iPhone photo on &lt;a href="https://getsnapshrink.com/heic-to-jpg/" rel="noopener noreferrer"&gt;getsnapshrink.com/heic-to-jpg/&lt;/a&gt; and watch DevTools → Network while it converts. Zero file uploads — that's the entire architecture, and HEIC didn't change it.&lt;/p&gt;

&lt;p&gt;First 10 images per session free, unlimited is a one-time $9. Happy to answer questions about the implementation in the comments.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>images</category>
      <category>privacy</category>
    </item>
  </channel>
</rss>
