<?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: swift king</title>
    <description>The latest articles on DEV Community by swift king (@jamiepark-design).</description>
    <link>https://dev.to/jamiepark-design</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%2F3994774%2F0c4a5fa7-1bef-409e-9359-16e5e4cbdc0e.png</url>
      <title>DEV Community: swift king</title>
      <link>https://dev.to/jamiepark-design</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jamiepark-design"/>
    <language>en</language>
    <item>
      <title>Barcode Quiet Zones: Why 5 Pallets Per Shift Got Sidelined</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Sun, 12 Jul 2026 09:15:29 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/barcode-quiet-zones-why-5-pallets-per-shift-got-sidelined-1pdf</link>
      <guid>https://dev.to/jamiepark-design/barcode-quiet-zones-why-5-pallets-per-shift-got-sidelined-1pdf</guid>
      <description>&lt;p&gt;Three years in an Amazon warehouse taught me one lesson about barcodes: the quiet zone matters more than print quality.&lt;/p&gt;

&lt;p&gt;Every shift, at least 5 pallets got flagged at inbound receiving. The labels looked fine to the human eye. But the laser scanner could not read them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Real Issue
&lt;/h2&gt;

&lt;p&gt;It was never about print resolution or contrast. The quiet zone — the blank space around the barcode — was too narrow. Most online generators do not add proper quiet zones by default.&lt;/p&gt;

&lt;p&gt;The rule from GS1: leave at least 10 times the narrow bar width on each side.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Actually Works
&lt;/h2&gt;

&lt;p&gt;I started using &lt;a href="https://genbarcode.org/" rel="noopener noreferrer"&gt;genbarcode.org&lt;/a&gt; which generates GS1-compliant barcodes with proper quiet zones built in. The site supports Code 128, EAN-13, UPC-A, ITF-14 — all the formats we used daily.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Barcode checklist:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GS1-registered prefix (not a reseller code)&lt;/li&gt;
&lt;li&gt;Proper quiet zone on all four sides&lt;/li&gt;
&lt;li&gt;Test scan with actual reader hardware&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Zero sidelined pallets after switching tools. Anyone else deal with barcode scanner rejections?&lt;/p&gt;

</description>
      <category>barcode</category>
      <category>logistics</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>WebP to PNG: How I Saved Our Email Campaign in 10 Minutes</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Sun, 12 Jul 2026 09:15:11 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/webp-to-png-how-i-saved-our-email-campaign-in-10-minutes-4adb</link>
      <guid>https://dev.to/jamiepark-design/webp-to-png-how-i-saved-our-email-campaign-in-10-minutes-4adb</guid>
      <description>&lt;p&gt;I spent weeks optimizing our landing page images as WebP. Page load dropped 40%. Lighthouse score hit 95.&lt;/p&gt;

&lt;p&gt;Then marketing sent the weekly newsletter. Every product image was broken.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem Nobody Talks About
&lt;/h2&gt;

&lt;p&gt;Email clients do not render WebP. Gmail, Outlook, Mailchimp — none of them support it. All that optimization meant nothing when our customers saw broken image placeholders.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Emergency Fix
&lt;/h2&gt;

&lt;p&gt;I batch-converted 200 product photos back to PNG in one go. The tool preserved alpha channels on transparent product shots, which was critical — our previous converter flattened them to white backgrounds.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Use Now
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://webp2png.io/" rel="noopener noreferrer"&gt;webp2png.io&lt;/a&gt; handles batch WebP-to-PNG conversion including transparency. No upload, runs in the browser.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My rule:&lt;/strong&gt; WebP for the web, PNG for everything else.&lt;/p&gt;

&lt;p&gt;What format headaches have you dealt with?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>webp</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>The Missing 180px Icon That Cost a Brand 6 Months of iPhone Impressions</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Fri, 10 Jul 2026 13:17:24 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/the-missing-180px-icon-that-cost-a-brand-6-months-of-iphone-impressions-1n9p</link>
      <guid>https://dev.to/jamiepark-design/the-missing-180px-icon-that-cost-a-brand-6-months-of-iphone-impressions-1n9p</guid>
      <description>&lt;p&gt;I audited a client site that had been live for six months. On a hunch, I added their site to my iPhone home screen.&lt;/p&gt;

&lt;p&gt;A gray letter placeholder. Six months of visitors bookmarking the site and seeing a generic icon.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Three Files Every Site Needs
&lt;/h2&gt;

&lt;p&gt;Most developers stop at favicon.ico. That covers browser tabs. But it does nothing for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;iPhone/iPad home screen bookmarks&lt;/li&gt;
&lt;li&gt;Android home screen shortcuts&lt;/li&gt;
&lt;li&gt;PWA install prompts&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The minimum set is three files:&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;link&lt;/span&gt; &lt;span class="na"&gt;rel=&lt;/span&gt;&lt;span class="s"&gt;"icon"&lt;/span&gt; &lt;span class="na"&gt;sizes=&lt;/span&gt;&lt;span class="s"&gt;"32x32"&lt;/span&gt; &lt;span class="na"&gt;href=&lt;/span&gt;&lt;span class="s"&gt;"/favicon-32x32.png"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel=&lt;/span&gt;&lt;span class="s"&gt;"apple-touch-icon"&lt;/span&gt; &lt;span class="na"&gt;sizes=&lt;/span&gt;&lt;span class="s"&gt;"180x180"&lt;/span&gt; &lt;span class="na"&gt;href=&lt;/span&gt;&lt;span class="s"&gt;"/apple-touch-icon.png"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;link&lt;/span&gt; &lt;span class="na"&gt;rel=&lt;/span&gt;&lt;span class="s"&gt;"manifest"&lt;/span&gt; &lt;span class="na"&gt;href=&lt;/span&gt;&lt;span class="s"&gt;"/site.webmanifest"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  One-Click Generation
&lt;/h2&gt;

&lt;p&gt;I use &lt;a href="https://genfavicon.org/" rel="noopener noreferrer"&gt;genfavicon.org&lt;/a&gt; to generate the complete package. It outputs all sizes plus the manifest in one download.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Quick audit:&lt;/strong&gt; Add your site to your iPhone home screen right now. If it is a gray letter, you are missing the apple-touch-icon.&lt;/p&gt;

&lt;p&gt;How long has your site been showing a placeholder?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>favicon</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Barcode Quiet Zones: Why 5 Pallets Per Shift Got Sidelined</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Fri, 10 Jul 2026 13:17:20 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/barcode-quiet-zones-why-5-pallets-per-shift-got-sidelined-17ch</link>
      <guid>https://dev.to/jamiepark-design/barcode-quiet-zones-why-5-pallets-per-shift-got-sidelined-17ch</guid>
      <description>&lt;p&gt;Three years in an Amazon warehouse taught me one lesson about barcodes: the quiet zone matters more than print quality.&lt;/p&gt;

&lt;p&gt;Every shift, at least 5 pallets got flagged at inbound receiving. The labels looked fine to the human eye. But the laser scanner could not read them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Real Issue
&lt;/h2&gt;

&lt;p&gt;It was never about print resolution or contrast. The quiet zone — the blank space around the barcode — was too narrow. Most online generators do not add proper quiet zones by default.&lt;/p&gt;

&lt;p&gt;The rule from GS1: leave at least 10 times the narrow bar width on each side.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Actually Works
&lt;/h2&gt;

&lt;p&gt;I started using &lt;a href="https://genbarcode.org/" rel="noopener noreferrer"&gt;genbarcode.org&lt;/a&gt; which generates GS1-compliant barcodes with proper quiet zones built in. The site supports Code 128, EAN-13, UPC-A, ITF-14 — all the formats we used daily.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Barcode checklist:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GS1-registered prefix (not a reseller code)&lt;/li&gt;
&lt;li&gt;Proper quiet zone on all four sides&lt;/li&gt;
&lt;li&gt;Test scan with actual reader hardware&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Zero sidelined pallets after switching tools. Anyone else deal with barcode scanner rejections?&lt;/p&gt;

</description>
      <category>barcode</category>
      <category>logistics</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>SVG to PNG: The DPI Setting That Kept Getting My Work Rejected</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Fri, 10 Jul 2026 13:13:44 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/svg-to-png-the-dpi-setting-that-kept-getting-my-work-rejected-4431</link>
      <guid>https://dev.to/jamiepark-design/svg-to-png-the-dpi-setting-that-kept-getting-my-work-rejected-4431</guid>
      <description>&lt;p&gt;A print shop rejected my client banner artwork three times. The reason? "72 DPI — unacceptable for print."&lt;/p&gt;

&lt;p&gt;The source file was a perfectly crisp vector SVG. Every export came out at web resolution because I never checked the DPI setting.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Fix That Changed Everything
&lt;/h2&gt;

&lt;p&gt;Most SVG-to-PNG converters default to 72 DPI because they target screen display. If you are exporting for print, you need 300 DPI minimum.&lt;/p&gt;

&lt;p&gt;I switched to specifying 300 DPI on every export. The same banner was accepted on the first re-submission.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Do It Now
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://svg2png.org/" rel="noopener noreferrer"&gt;svg2png.org&lt;/a&gt; lets you specify export resolution. One SVG source, any DPI output — 1x for web, 3x for retina, 300 DPI for print.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Checklist before exporting SVG to PNG:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who is the audience? Screen or print?&lt;/li&gt;
&lt;li&gt;What DPI does the destination require?&lt;/li&gt;
&lt;li&gt;Does the converter preserve transparency?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This one setting has saved me hours of rework. Anyone else had print shops reject web-resolution files?&lt;/p&gt;

</description>
      <category>svg</category>
      <category>webdev</category>
      <category>design</category>
    </item>
    <item>
      <title>WebP to PNG: How I Saved Our Email Campaign in 10 Minutes</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Fri, 10 Jul 2026 13:13:42 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/webp-to-png-how-i-saved-our-email-campaign-in-10-minutes-14mf</link>
      <guid>https://dev.to/jamiepark-design/webp-to-png-how-i-saved-our-email-campaign-in-10-minutes-14mf</guid>
      <description>&lt;p&gt;I spent weeks optimizing our landing page images as WebP. Page load dropped 40%. Lighthouse score hit 95.&lt;/p&gt;

&lt;p&gt;Then marketing sent the weekly newsletter. Every product image was broken.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem Nobody Talks About
&lt;/h2&gt;

&lt;p&gt;Email clients do not render WebP. Gmail, Outlook, Mailchimp — none of them support it. All that optimization meant nothing when our customers saw broken image placeholders.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Emergency Fix
&lt;/h2&gt;

&lt;p&gt;I batch-converted 200 product photos back to PNG in one go. The tool preserved alpha channels on transparent product shots, which was critical — our previous converter flattened them to white backgrounds.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Use Now
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://webp2png.io/" rel="noopener noreferrer"&gt;webp2png.io&lt;/a&gt; handles batch WebP-to-PNG conversion including transparency. No upload, runs in the browser.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My rule:&lt;/strong&gt; WebP for the web, PNG for everything else.&lt;/p&gt;

&lt;p&gt;What format headaches have you dealt with?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>webp</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>From 8.2s to 2.1s: Image Compression Changed a Store Conversion Rate</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Wed, 08 Jul 2026 15:23:09 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/from-82s-to-21s-image-compression-changed-a-store-conversion-rate-4l8l</link>
      <guid>https://dev.to/jamiepark-design/from-82s-to-21s-image-compression-changed-a-store-conversion-rate-4l8l</guid>
      <description>&lt;p&gt;Audited a Shopify store. Homepage: 22MB. Product images: 4MB each. Load time: 8.2 seconds.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Fix
&lt;/h2&gt;

&lt;p&gt;Lossless compression. Same quality. 4MB to 400KB per image. Load time dropped to 2.1 seconds.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://compress2png.com/" rel="noopener noreferrer"&gt;compress2png.com&lt;/a&gt; handles lossless PNG compression in the browser. No upload needed.&lt;/p&gt;

&lt;p&gt;Run Lighthouse before and after compressing. The score jump alone is worth showing clients.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>performance</category>
      <category>images</category>
    </item>
    <item>
      <title>The Missing 180px Icon That Cost a Brand 6 Months of iPhone Impressions</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Wed, 08 Jul 2026 15:22:11 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/the-missing-180px-icon-that-cost-a-brand-6-months-of-iphone-impressions-4gb6</link>
      <guid>https://dev.to/jamiepark-design/the-missing-180px-icon-that-cost-a-brand-6-months-of-iphone-impressions-4gb6</guid>
      <description>&lt;p&gt;I audited a client site live for six months. Added it to my iPhone home screen. Gray letter placeholder.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Three Files Every Site Needs
&lt;/h2&gt;

&lt;p&gt;Most devs stop at favicon.ico. That does nothing for iOS or Android bookmarks.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://genfavicon.org/" rel="noopener noreferrer"&gt;genfavicon.org&lt;/a&gt; generates the complete package in one download.&lt;/p&gt;

&lt;p&gt;Add your site to your iPhone home screen right now. Is it a gray letter?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>favicon</category>
    </item>
    <item>
      <title>Barcode Quiet Zones: Why 5 Pallets Per Shift Got Sidelined</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Wed, 08 Jul 2026 15:22:05 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/barcode-quiet-zones-why-5-pallets-per-shift-got-sidelined-4l1</link>
      <guid>https://dev.to/jamiepark-design/barcode-quiet-zones-why-5-pallets-per-shift-got-sidelined-4l1</guid>
      <description>&lt;p&gt;Three years in an Amazon warehouse taught me one lesson: the quiet zone matters more than print quality.&lt;/p&gt;

&lt;p&gt;Every shift, at least 5 pallets got flagged at inbound receiving. The labels looked fine but the laser scanner could not read them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Real Issue
&lt;/h2&gt;

&lt;p&gt;The quiet zone — the blank space around the barcode — was too narrow. GS1 requires at least 10x the narrow bar width on each side.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Actually Works
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://genbarcode.org/" rel="noopener noreferrer"&gt;genbarcode.org&lt;/a&gt; generates GS1-compliant barcodes with proper quiet zones built in. Code 128, EAN-13, UPC-A, ITF-14 — all supported.&lt;/p&gt;

&lt;p&gt;Zero sidelined pallets after switching.&lt;/p&gt;

</description>
      <category>barcode</category>
      <category>logistics</category>
    </item>
    <item>
      <title>Trailing Comma Took Down Production at 11 PM — A JSON Debugging Story</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Wed, 08 Jul 2026 15:21:30 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/trailing-comma-took-down-production-at-11-pm-a-json-debugging-story-2n2m</link>
      <guid>https://dev.to/jamiepark-design/trailing-comma-took-down-production-at-11-pm-a-json-debugging-story-2n2m</guid>
      <description>&lt;p&gt;The deploy failed at 11 PM with a cryptic error: "Unexpected token } in JSON at position 5824."&lt;/p&gt;

&lt;p&gt;Two developers stared at the minified config file for ten minutes. Line 247. A trailing comma in a 200KB JSON object.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Minified JSON Is a Trap
&lt;/h2&gt;

&lt;p&gt;Minified JSON saves bandwidth but costs debugging time. When everything is on one line, a syntax error is invisible.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I do now:&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Beautify JSON before any code review&lt;/li&gt;
&lt;li&gt;Validate syntax before every deploy&lt;/li&gt;
&lt;li&gt;Never debug minified output directly&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The Tool That Saves Me
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://formlyapp.org/" rel="noopener noreferrer"&gt;formlyapp.org&lt;/a&gt; does all three in the browser. It formats, validates, and highlights errors instantly. No data leaves your machine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;My pre-deploy checklist:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;json.loads()&lt;/code&gt; the config file&lt;/li&gt;
&lt;li&gt;Run it through a formatter&lt;/li&gt;
&lt;li&gt;Only minify as the final build step&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What is your worst production JSON debugging story?&lt;/p&gt;

</description>
      <category>json</category>
      <category>webdev</category>
      <category>debugging</category>
    </item>
    <item>
      <title>SVG to PNG: The DPI Setting That Kept Getting My Work Rejected</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Wed, 08 Jul 2026 15:21:22 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/svg-to-png-the-dpi-setting-that-kept-getting-my-work-rejected-480n</link>
      <guid>https://dev.to/jamiepark-design/svg-to-png-the-dpi-setting-that-kept-getting-my-work-rejected-480n</guid>
      <description>&lt;p&gt;A print shop rejected my client banner artwork three times. The reason? "72 DPI — unacceptable for print."&lt;/p&gt;

&lt;p&gt;The source file was a perfectly crisp vector SVG. Every export came out at web resolution because I never checked the DPI setting.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Fix That Changed Everything
&lt;/h2&gt;

&lt;p&gt;Most SVG-to-PNG converters default to 72 DPI because they target screen display. If you are exporting for print, you need 300 DPI minimum.&lt;/p&gt;

&lt;p&gt;I switched to specifying 300 DPI on every export. The same banner was accepted on the first re-submission.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Do It Now
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://svg2png.org/" rel="noopener noreferrer"&gt;svg2png.org&lt;/a&gt; lets you specify export resolution. One SVG source, any DPI output — 1x for web, 3x for retina, 300 DPI for print.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Checklist before exporting SVG to PNG:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who is the audience? Screen or print?&lt;/li&gt;
&lt;li&gt;What DPI does the destination require?&lt;/li&gt;
&lt;li&gt;Does the converter preserve transparency?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This one setting has saved me hours of rework. Anyone else had print shops reject web-resolution files?&lt;/p&gt;

</description>
      <category>svg</category>
      <category>webdev</category>
      <category>design</category>
    </item>
    <item>
      <title>WebP to PNG: How I Saved Our Email Campaign in 10 Minutes</title>
      <dc:creator>swift king</dc:creator>
      <pubDate>Wed, 08 Jul 2026 15:20:58 +0000</pubDate>
      <link>https://dev.to/jamiepark-design/webp-to-png-how-i-saved-our-email-campaign-in-10-minutes-34of</link>
      <guid>https://dev.to/jamiepark-design/webp-to-png-how-i-saved-our-email-campaign-in-10-minutes-34of</guid>
      <description>&lt;p&gt;WebP cut our page load 40%. Then our email campaign went out with broken images. Email clients do not render WebP.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Fix
&lt;/h2&gt;

&lt;p&gt;Batch converted everything back to PNG via webp2png.io.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson
&lt;/h2&gt;

&lt;p&gt;Always have a PNG fallback.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>webp</category>
    </item>
  </channel>
</rss>
