<?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: GANESH</title>
    <description>The latest articles on DEV Community by GANESH (@tmlganesh).</description>
    <link>https://dev.to/tmlganesh</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%2F3829424%2Fe5b69997-ecdb-4bd4-b695-c853f11aff35.png</url>
      <title>DEV Community: GANESH</title>
      <link>https://dev.to/tmlganesh</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tmlganesh"/>
    <language>en</language>
    <item>
      <title>I tried to make text invisible to cameras (but readable to humans)</title>
      <dc:creator>GANESH</dc:creator>
      <pubDate>Tue, 17 Mar 2026 12:46:44 +0000</pubDate>
      <link>https://dev.to/tmlganesh/i-tried-to-make-text-invisible-to-cameras-but-readable-to-humans-p73</link>
      <guid>https://dev.to/tmlganesh/i-tried-to-make-text-invisible-to-cameras-but-readable-to-humans-p73</guid>
      <description>&lt;p&gt;We spend a lot of time thinking about backend security,auth, encryption, access control.&lt;/p&gt;

&lt;p&gt;But there’s a simple gap on the frontend:&lt;/p&gt;

&lt;p&gt;If something is visible on screen, it can be captured with a phone.&lt;/p&gt;

&lt;p&gt;There’s no reliable way on the web to prevent that. At best, you can try to block screenshots or disable interactions, but none of that works against an external camera.&lt;/p&gt;

&lt;p&gt;I wanted to explore a different direction.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The idea&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Instead of trying to block access, I experimented with how text is rendered.&lt;/p&gt;

&lt;p&gt;The key observation is that human vision and cameras behave differently:&lt;/p&gt;

&lt;p&gt;Humans perceive continuous motion (persistence of vision)&lt;/p&gt;

&lt;p&gt;Cameras capture discrete frames&lt;/p&gt;

&lt;p&gt;So I tried rendering text in a way that stays readable to the human eye but doesn’t translate cleanly into individual frames.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I built&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A small library called &lt;strong&gt;secure-render-text&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It uses a combination of:&lt;/p&gt;

&lt;p&gt;rapid frame alternation&lt;/p&gt;

&lt;p&gt;layered character rendering&lt;/p&gt;

&lt;p&gt;subtle visual inconsistencies&lt;/p&gt;

&lt;p&gt;The goal isn’t to hide the text, but to make captured output less clean and less reliable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where this might be useful&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Internal dashboards with sensitive data&lt;/p&gt;

&lt;p&gt;SaaS tools where screen leakage is a concern&lt;/p&gt;

&lt;p&gt;Exam or assessment interfaces&lt;/p&gt;

&lt;p&gt;Situations where you want to reduce casual capture&lt;/p&gt;

&lt;p&gt;Git Hub  : &lt;a href="https://github.com/tmlganesh/npm-package_secure-render-text" rel="noopener noreferrer"&gt;https://github.com/tmlganesh/npm-package_secure-render-text&lt;/a&gt;&lt;br&gt;
NPM      : &lt;a href="https://www.npmjs.com/package/secure-render-text" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/secure-render-text&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>react</category>
      <category>opensource</category>
      <category>community</category>
    </item>
  </channel>
</rss>
