<?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: svpg</title>
    <description>The latest articles on DEV Community by svpg (@acrazing).</description>
    <link>https://dev.to/acrazing</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F46439%2F71f09672-ae7f-4121-9dc0-b7ce6d63e555.jpeg</url>
      <title>DEV Community: svpg</title>
      <link>https://dev.to/acrazing</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/acrazing"/>
    <language>en</language>
    <item>
      <title>Advanced Formatting for Messy JSON from Anywhere in Chrome</title>
      <dc:creator>svpg</dc:creator>
      <pubDate>Fri, 08 May 2026 15:58:05 +0000</pubDate>
      <link>https://dev.to/acrazing/advanced-formatting-for-messy-json-from-anywhere-in-chrome-4ib</link>
      <guid>https://dev.to/acrazing/advanced-formatting-for-messy-json-from-anywhere-in-chrome-4ib</guid>
      <description>&lt;p&gt;Messy JSON rarely lives in a clean file. It shows up inside API error pages, copied debug output, selected text, DOM elements, raw responses, and clipboard snippets.&lt;/p&gt;

&lt;p&gt;It also often contains JSON inside JSON string fields:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"foo"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"{&lt;/span&gt;&lt;span class="se"&gt;\"&lt;/span&gt;&lt;span class="s2"&gt;bar&lt;/span&gt;&lt;span class="se"&gt;\"&lt;/span&gt;&lt;span class="s2"&gt;:1}"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A normal JSON formatter usually makes the outer object readable, but the useful part is still trapped inside an escaped string:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"foo"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"{&lt;/span&gt;&lt;span class="se"&gt;\"&lt;/span&gt;&lt;span class="s2"&gt;bar&lt;/span&gt;&lt;span class="se"&gt;\"&lt;/span&gt;&lt;span class="s2"&gt;:1}"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;RawLens is an open-source Chrome extension for advanced formatting of messy JSON from anywhere in the browser. It detects JSON-looking string fields and pretty-prints them as structured data, so the nested value becomes readable instead of staying a giant escaped string.&lt;/p&gt;

&lt;p&gt;Conceptually, the example becomes much closer to this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"foo"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"bar"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The other core feature is speed. You do not have to move the content into a separate formatter first. RawLens can inspect the exact thing you are looking at:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;selected text&lt;/li&gt;
&lt;li&gt;a hovered page element&lt;/li&gt;
&lt;li&gt;clipboard content&lt;/li&gt;
&lt;li&gt;current page source or page HTML&lt;/li&gt;
&lt;li&gt;raw pages opened directly in Chrome&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That makes it useful for API responses, embedded log payloads, copied production errors, and web pages where only one selected blob matters.&lt;/p&gt;

&lt;p&gt;It also supports ANSI logs, HTML, CSS, YAML, JavaScript, diffs, and other source-like text. Those formats are useful extra coverage, but the main feature is fast inspection of selection/element/clipboard content plus nested JSON string formatting.&lt;/p&gt;

&lt;p&gt;RawLens runs locally in the browser. It does not upload logs to a server and does not collect log data.&lt;/p&gt;

&lt;p&gt;Chrome Web Store:&lt;br&gt;
&lt;a href="https://chromewebstore.google.com/detail/rawlens/lbnkfmnolbefifdccejjijdgdipnfaib" rel="noopener noreferrer"&gt;https://chromewebstore.google.com/detail/rawlens/lbnkfmnolbefifdccejjijdgdipnfaib&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;GitHub:&lt;br&gt;
&lt;a href="https://github.com/RawLens/rawlens" rel="noopener noreferrer"&gt;https://github.com/RawLens/rawlens&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Website:&lt;br&gt;
&lt;a href="https://rawlens.github.io/rawlens/" rel="noopener noreferrer"&gt;https://rawlens.github.io/rawlens/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Feedback is especially welcome from people who regularly deal with escaped or nested JSON in logs, selected page text, page elements, or copied debug output.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>chrome</category>
      <category>debugging</category>
    </item>
  </channel>
</rss>
