<?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: Amanuel Kidu </title>
    <description>The latest articles on DEV Community by Amanuel Kidu  (@amanuel_snit_e92602511eb4).</description>
    <link>https://dev.to/amanuel_snit_e92602511eb4</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%2F4011305%2F5dbfe0cc-8b8b-4a6a-843c-8817940869a3.png</url>
      <title>DEV Community: Amanuel Kidu </title>
      <link>https://dev.to/amanuel_snit_e92602511eb4</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/amanuel_snit_e92602511eb4"/>
    <language>en</language>
    <item>
      <title>How I Built a Free Image Toolkit : freeimgkit (Next.js + WebAssembly)</title>
      <dc:creator>Amanuel Kidu </dc:creator>
      <pubDate>Wed, 01 Jul 2026 19:24:53 +0000</pubDate>
      <link>https://dev.to/amanuel_snit_e92602511eb4/how-i-built-a-free-image-toolkit-freeimgkit-nextjs-webassembly-47g</link>
      <guid>https://dev.to/amanuel_snit_e92602511eb4/how-i-built-a-free-image-toolkit-freeimgkit-nextjs-webassembly-47g</guid>
      <description>&lt;p&gt;I recently launched FreeImgKit — a collection of free &lt;br&gt;
online image tools that run entirely in the browser. &lt;br&gt;
No server processing, no account needed.&lt;/p&gt;

&lt;p&gt;Here's what I built and the technical decisions behind it.&lt;/p&gt;
&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;FreeImgKit has 6 tools:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Image compressor (JPG, PNG, WebP)&lt;/li&gt;
&lt;li&gt;Image resizer with aspect ratio lock&lt;/li&gt;
&lt;li&gt;Photo cropper with preset ratios&lt;/li&gt;
&lt;li&gt;Format converter (PNG↔JPG↔WebP)&lt;/li&gt;
&lt;li&gt;Social media resizer (all platform presets)&lt;/li&gt;
&lt;li&gt;AI background remover&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
  
  
  The core technical decision: client-side only
&lt;/h2&gt;

&lt;p&gt;Most image tools upload your file to a server, &lt;br&gt;
process it, and send it back. This has two problems:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Privacy — your images are stored on someone's server&lt;/li&gt;
&lt;li&gt;Speed — upload time adds latency&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I decided everything would run in the browser instead.&lt;/p&gt;
&lt;h2&gt;
  
  
  How each tool works
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Compression, resizing, cropping, converting&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;These all use the browser's built-in Canvas API:&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="nx"&gt;canvas&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createElement&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;canvas&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;ctx&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;canvas&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getContext&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;2d&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="nx"&gt;canvas&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;width&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;targetWidth&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nx"&gt;canvas&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;height&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;targetHeight&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nx"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;drawImage&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;img&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;targetWidth&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;targetHeight&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="nx"&gt;canvas&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toBlob&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;blob&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="c1"&gt;// blob is the processed image&lt;/span&gt;
&lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;image/webp&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;quality&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For compression I used the &lt;code&gt;browser-image-compression&lt;/code&gt; &lt;br&gt;
npm package which handles the quality/size tradeoff &lt;br&gt;
automatically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI Background Removal via WebAssembly&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This was the most interesting part. Background removal &lt;br&gt;
needs a real ML model — but I didn't want to send &lt;br&gt;
images to a server.&lt;/p&gt;

&lt;p&gt;The solution: &lt;code&gt;@imgly/background-removal&lt;/code&gt; — a package &lt;br&gt;
that runs a segmentation model via WebAssembly directly &lt;br&gt;
in the browser.&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="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;removeBackground&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@imgly/background-removal&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;blob&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;removeBackground&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;imageFile&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="c1"&gt;// blob is a transparent PNG — no server involved&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The first run downloads the model (~50MB) to the &lt;br&gt;
browser cache. After that it's instant. The quality &lt;br&gt;
is comparable to paid tools like remove.bg for most &lt;br&gt;
subjects.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tech stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Next.js 14&lt;/strong&gt; App Router + TypeScript&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tailwind CSS&lt;/strong&gt; for styling&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Canvas API&lt;/strong&gt; for image processing&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;a class="mentioned-user" href="https://dev.to/imgly"&gt;@imgly&lt;/a&gt;/background-removal&lt;/strong&gt; for AI bg removal&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;browser-image-compression&lt;/strong&gt; for compression&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vercel&lt;/strong&gt; for deployment&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare&lt;/strong&gt; for CDN&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  SEO architecture
&lt;/h2&gt;

&lt;p&gt;Each tool is a separate page with its own URL:&lt;br&gt;
Each page has unique metadata, FAQ schema markup, &lt;br&gt;
and detailed SEO content explaining when and why &lt;br&gt;
to use that specific tool. This programmatic SEO &lt;br&gt;
approach means each conversion pair targets its &lt;br&gt;
own search query.&lt;/p&gt;

&lt;h2&gt;
  
  
  Results so far
&lt;/h2&gt;

&lt;p&gt;Launched 5 weeks ago:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;13 pages indexed by Google&lt;/li&gt;
&lt;li&gt;845 impressions in first month&lt;/li&gt;
&lt;li&gt;Already ranking for "png to jpg", "crop photo online"&lt;/li&gt;
&lt;li&gt;69 unique visitors in first 28 days&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Still early but the organic growth curve is heading &lt;br&gt;
in the right direction.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do differently
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Build the conversion pages first — they get more 
search traffic than the general tools&lt;/li&gt;
&lt;li&gt;Add the FAQ schema from day one — Google detected 
it immediately and it boosts CTR&lt;/li&gt;
&lt;li&gt;Submit sitemap earlier — I waited 3 weeks before 
submitting and lost indexing time&lt;/li&gt;
&lt;/ol&gt;

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

&lt;p&gt;👉 &lt;a href="https://freeimgkit.com" rel="noopener noreferrer"&gt;freeimgkit.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;All tools are free, no account needed, and your &lt;br&gt;
images never leave your device.&lt;/p&gt;

&lt;p&gt;Would love feedback from the dev community — &lt;br&gt;
especially on the WASM background removal &lt;br&gt;
performance on different devices.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>nextjs</category>
      <category>showdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
