<?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: Pixelquil</title>
    <description>The latest articles on DEV Community by Pixelquil (@pixelquil).</description>
    <link>https://dev.to/pixelquil</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%2F4081574%2F182616a0-6459-4496-bcdf-4c57f008ddef.png</url>
      <title>DEV Community: Pixelquil</title>
      <link>https://dev.to/pixelquil</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pixelquil"/>
    <language>en</language>
    <item>
      <title>I Built Pixelquil: Free Browser Tools for SVG, JSON, and Technical SEO (No Signup, No Uploads)</title>
      <dc:creator>Pixelquil</dc:creator>
      <pubDate>Mon, 17 Aug 2026 12:03:06 +0000</pubDate>
      <link>https://dev.to/pixelquil/i-built-pixelquil-free-browser-tools-for-svg-json-and-technical-seo-no-signup-no-uploads-mep</link>
      <guid>https://dev.to/pixelquil/i-built-pixelquil-free-browser-tools-for-svg-json-and-technical-seo-no-signup-no-uploads-mep</guid>
      <description>&lt;p&gt;I kept running into the same small problem while working on client sites and my own projects: I needed a quick tool to fix a broken SVG, format a messy JSON blob, or check a robots.txt file, and every free option online either wanted me to sign up first or uploaded my file to their server before showing me anything.&lt;/p&gt;

&lt;p&gt;So I built &lt;a href="https://pixelquil.com" rel="noopener noreferrer"&gt;Pixelquil&lt;/a&gt;, a small toolkit that runs entirely in the browser. No account, no upload, no server processing your file. Whatever you paste in stays on your device.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in it right now
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;SVG tools&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SVG editor and viewer&lt;/li&gt;
&lt;li&gt;viewBox fixer (for that classic "my icon is cut off" problem)&lt;/li&gt;
&lt;li&gt;Color palette extractor&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Developer tools&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;JSON formatter and validator&lt;/li&gt;
&lt;li&gt;JWT decoder&lt;/li&gt;
&lt;li&gt;Regex tester and builder&lt;/li&gt;
&lt;li&gt;UUID and hash generators&lt;/li&gt;
&lt;li&gt;Password and passphrase generator&lt;/li&gt;
&lt;li&gt;Case converter, Unix timestamp converter, text diff checker, cron expression parser, and a few more&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;SEO tools&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;robots.txt tester&lt;/li&gt;
&lt;li&gt;AI crawler access checker&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why client side only
&lt;/h2&gt;

&lt;p&gt;Two reasons, honestly. First, privacy. A lot of the files people run through these tools come from client work, and I did not want to be the reason someone's unreleased product SVG or a JWT with real claims in it ends up sitting on some server's logs. Second, speed. Client side tools respond instantly. No upload spinner, no waiting on a request round trip for something that should take milliseconds.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;More tools are getting added as I run into more of these small tasks myself. If you have a tool you keep wishing existed but never bothered to look for, drop it in the comments. That is genuinely how most of the current list got built.&lt;/p&gt;

&lt;p&gt;Try it here: &lt;a href="https://pixelquil.com" rel="noopener noreferrer"&gt;pixelquil.com&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
