<?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: Akok</title>
    <description>The latest articles on DEV Community by Akok (@978190375).</description>
    <link>https://dev.to/978190375</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%2F4209198%2F129b6618-8e48-4af0-b1bd-3e4c8ca23229.jpg</url>
      <title>DEV Community: Akok</title>
      <link>https://dev.to/978190375</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/978190375"/>
    <language>en</language>
    <item>
      <title>Screen Recording Has No Sound? 6 Common Causes on Mac and Windows</title>
      <dc:creator>Akok</dc:creator>
      <pubDate>Sun, 15 Nov 2026 14:01:23 +0000</pubDate>
      <link>https://dev.to/978190375/screen-recording-has-no-sound-6-common-causes-on-mac-and-windows-23c4</link>
      <guid>https://dev.to/978190375/screen-recording-has-no-sound-6-common-causes-on-mac-and-windows-23c4</guid>
      <description>&lt;p&gt;You record a few minutes of a workflow, hit play, and it is completely silent. Almost everyone who records their screen has been there.&lt;/p&gt;

&lt;p&gt;Before you troubleshoot, separate two things, because most "no sound" problems come from mixing them up:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;System audio&lt;/strong&gt;: whatever the computer itself plays — videos, music, the other person's voice in a call.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Microphone&lt;/strong&gt;: your own voice.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Often only one of the two was recorded while you assumed both were. Here are the causes, roughly in order of how often they come up.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. On a Mac, the built-in recorder captures the microphone, not system audio
&lt;/h2&gt;

&lt;p&gt;macOS's built-in screen recording (the toolbar from the screenshot shortcut, and QuickTime Player's "New Screen Recording") lets you choose a microphone, but it does &lt;strong&gt;not&lt;/strong&gt; capture the sound your Mac is playing. If you recorded a demo that includes a video with music, a silent result is expected behavior, not a bug.&lt;/p&gt;

&lt;p&gt;Your options:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Narrate instead.&lt;/strong&gt; If you only need your voice, the built-in tool is enough.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use a virtual audio driver.&lt;/strong&gt; Free drivers such as BlackHole route system audio into a virtual input that a recorder can pick up. You usually have to build a "multi-output device" so you can still hear the sound yourself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use a recorder that captures system audio directly.&lt;/strong&gt; OBS can do this on recent macOS versions, and some dedicated screen recorders have it built in.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  2. On Windows, Xbox Game Bar records one app at a time
&lt;/h2&gt;

&lt;p&gt;Game Bar (Win + G) can capture system sound and the microphone, but it records a single app window and is designed for games. If you try to record the whole desktop, File Explorer, or a workflow that switches between windows, it may refuse or only capture one window.&lt;/p&gt;

&lt;p&gt;For full-desktop recording with system sound, use OBS or another recorder that supports "whole screen + system audio". Some sound drivers also expose a "Stereo Mix" input, but that depends on your hardware and is often disabled or missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The app doesn't have microphone permission
&lt;/h2&gt;

&lt;p&gt;Both systems have a per-app microphone switch:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;macOS&lt;/strong&gt;: System Settings → Privacy &amp;amp; Security → Microphone. Make sure the recorder is listed and on. If you clicked "Don't Allow" once, the system will not ask again — you have to turn it on here, and the app usually needs a restart afterwards.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Windows&lt;/strong&gt;: Settings → Privacy &amp;amp; security → Microphone. Check that microphone access and "Let apps access your microphone" are on, and that your recorder isn't switched off in the app list.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A typical symptom of a blocked microphone: the video has an audio track, but the level is perfectly flat.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. The wrong input device is selected
&lt;/h2&gt;

&lt;p&gt;A computer can have several "microphones": the built-in one, headphones, a webcam, a monitor, a virtual device. The recorder's default isn't always the one you are speaking into.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Check which device the recorder is using.&lt;/li&gt;
&lt;li&gt;In the system sound settings, speak and watch the input level meter. If it doesn't move, the wrong device is selected or it is muted.&lt;/li&gt;
&lt;li&gt;After plugging or unplugging hardware, the system sometimes changes the default input on its own. Check again before recording.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Bluetooth headphones switch modes when the mic turns on
&lt;/h2&gt;

&lt;p&gt;Bluetooth headphones use a high-quality profile for listening only. As soon as the headset microphone is also used, many of them drop into a call profile with a much lower sample rate. The result can be muffled sound, noise, or audio that suddenly disappears from your headphones.&lt;/p&gt;

&lt;p&gt;A safer setup is wired headphones, or the computer's own microphone for recording with the Bluetooth headset used only for listening.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. There is sound, but it doesn't match the picture
&lt;/h2&gt;

&lt;p&gt;If audio runs a few hundred milliseconds early or late, usual suspects are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the computer was under heavy load, so video frames were dropped while audio was not;&lt;/li&gt;
&lt;li&gt;a virtual audio device or Bluetooth device adds its own delay;&lt;/li&gt;
&lt;li&gt;the frame rate is set higher than the machine can keep up with.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Lower the frame rate and resolution, close heavy background apps, and record a short test. If you use Bluetooth, try wired for comparison.&lt;/p&gt;

&lt;h2&gt;
  
  
  A 30-second test before every long recording
&lt;/h2&gt;

&lt;p&gt;Most "I recorded half an hour with no sound" accidents can be caught in seconds:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start recording, say "test", and play a short clip with sound.&lt;/li&gt;
&lt;li&gt;Stop and play it back. Check that both sources are there and the levels are reasonable.&lt;/li&gt;
&lt;li&gt;Then record for real.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Disclosure
&lt;/h2&gt;

&lt;p&gt;I build InSnap, a screenshot and screen-recording app for Mac and Windows. Its recording panel has separate switches for the microphone and system audio, plus a live microphone level, which makes some of the checks above quicker. The troubleshooting above applies to any recorder.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn6ej7tvhmktgp67z76dj.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn6ej7tvhmktgp67z76dj.jpg" alt="The recording panel with separate microphone and system-audio controls" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Why can't my Mac record system audio?&lt;/strong&gt; macOS's built-in recorder only offers microphone input. You need a virtual audio driver or a recorder that captures system audio directly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why do I only hear my microphone on Windows?&lt;/strong&gt; Check whether you are recording the whole screen or a single app. Game Bar records one app. Whole-screen recording needs a tool with system-audio support, or a "Stereo Mix" input if your sound driver offers one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The audio is recorded but very quiet. What now?&lt;/strong&gt; Raise the input volume in system sound settings, move closer to the microphone, or normalize the volume in a video editor.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I add the voice afterwards?&lt;/strong&gt; Yes, with any video editor. Matching timing to the actions takes time, so narrating while recording is easier when possible.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Details about built-in tools are based on Apple's and Microsoft's public documentation and common recorder documentation as of November 2026. Exact buttons and options depend on your system version.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>productivity</category>
      <category>tools</category>
      <category>macos</category>
    </item>
    <item>
      <title>Why OCR Returns the Wrong Word Instead of an Error</title>
      <dc:creator>Akok</dc:creator>
      <pubDate>Wed, 28 Oct 2026 18:18:34 +0000</pubDate>
      <link>https://dev.to/978190375/why-ocr-returns-the-wrong-word-instead-of-an-error-5423</link>
      <guid>https://dev.to/978190375/why-ocr-returns-the-wrong-word-instead-of-an-error-5423</guid>
      <description>&lt;p&gt;Copying text out of a screenshot usually works, and that is the problem. When it fails, it rarely fails loudly. There is no red underline, no "could not recognise text", no empty box. There is a sentence that reads perfectly well — except for one character, and that character changes the meaning.&lt;/p&gt;

&lt;p&gt;This is why people paste an order number that is off by a digit, a config key with a wrong letter, or a sentence in a document with a character that was never there. The recognition did not crash. It guessed confidently.&lt;/p&gt;

&lt;h2&gt;
  
  
  Recognition is a classifier, not a parser
&lt;/h2&gt;

&lt;p&gt;It helps to know what the engine actually does. Text recognition splits the image into lines, then into character-shaped regions, then runs each region through a classifier that returns the most likely character. That classifier never says "I don't know". It always returns the closest match it can find.&lt;/p&gt;

&lt;p&gt;At good input quality, that closest match is right almost everywhere. At poor quality, the closest match is a different character that happens to look similar: an &lt;code&gt;a&lt;/code&gt; that could be an &lt;code&gt;o&lt;/code&gt;, a &lt;code&gt;1&lt;/code&gt; that could be an &lt;code&gt;l&lt;/code&gt;, or one CJK character that could easily be mistaken for a neighbour with a shared component. The engine has no idea it is wrong.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5cjju86gjmxjsahd8qad.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5cjju86gjmxjsahd8qad.jpg" alt="Running text recognition on a screenshot" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What makes the input "poor"
&lt;/h2&gt;

&lt;p&gt;Four things matter, in roughly this order:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Text height in pixels.&lt;/strong&gt; Smaller text has fewer pixels to classify. This is the big one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The character set.&lt;/strong&gt; Chinese, Japanese and Korean characters are dense; a few lost pixels change both the shape and the identity of the character. Latin letters are simpler and survive longer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Anti-aliasing and scaling.&lt;/strong&gt; Every resize blends the edges of every stroke. One resize is fine; three, stacked, lose the shape.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contrast and background.&lt;/strong&gt; Grey-on-white and light-on-dark both reduce edge strength. So do gradients and photos behind the text.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most of the failure reports come from the first one, and the fix is usually to capture more pixels, not to try harder.&lt;/p&gt;

&lt;p&gt;InSnap has no separate accuracy setting. It works on the pixels you select: a 1x screenshot of a dense UI already has each line at the height the screen drew it, and a 2x Retina capture has double that. The difference between the two, for a given paragraph of text, is often the difference between correct and plausible-but-wrong.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn3xswrzc00913axtpssi.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn3xswrzc00913axtpssi.jpg" alt="Reading a detail with the magnifier" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the practical line sits
&lt;/h2&gt;

&lt;p&gt;To see the boundary rather than guess at it, it is worth building a small, repeatable test: render the same sentence at several text heights, run the recognition on each, and compare the output to the input character by character. That is exactly what the two images below do, using real output from a local engine, not made-up examples.&lt;/p&gt;

&lt;p&gt;The Chinese line and the English line were rendered at five heights and recognised fresh each time. Red marks the characters that differ from the original.&lt;/p&gt;

&lt;p&gt;Two things come out of it. First, the line is correct until it is not: there is no gradual degradation, just a size below which the wrong character appears. Second, the two scripts break at different points. Latin text slipped earlier here, while Chinese held on longer, which is the opposite of what most people assume from "Chinese is harder".&lt;/p&gt;

&lt;p&gt;When the same sentence is recognised at even smaller sizes, the output becomes a different kind of wrong. Not empty, not gibberish, but a real sentence with real, wrong characters:&lt;/p&gt;

&lt;p&gt;That second image is the useful one. It shows what a wrong result actually looks like: not obvious enough to notice, not subtle enough to be nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to catch it before it reaches a document
&lt;/h2&gt;

&lt;p&gt;The recognition cannot tell you it is unsure, so you have to check in places where a wrong character is expensive.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Check anything with numbers or identifiers.&lt;/strong&gt; Order IDs, licence keys, version strings, invoice totals. A single wrong digit is invisible in context and fatal downstream.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the length.&lt;/strong&gt; A two-character identifier that came back as three, or the reverse, is a reliable signal that something went wrong.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check unusual characters.&lt;/strong&gt; Pipes, spaces, non-breaking spaces, Cyrillic versus Latin confusion. If the text is code, pasting into a monospace view makes these obvious.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check the edges.&lt;/strong&gt; Characters at the start or end of a line are the first to be cut off during detection. If a line ends abruptly, look at the last one or two characters.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recapture at a larger size, do not upscale.&lt;/strong&gt; Upscaling a blurry line does not create detail, and it rarely fixes a wrong character. Recapturing the same area at 2x, or zooming the source before capturing, does.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The practical corollary is that a screenshot taken with a wide selection at good resolution is easier to recognise than a tiny one cropped tightly. Cropping reduces noise, but shrinking reduces information, and information is what the classifier eats.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you can rely on
&lt;/h2&gt;

&lt;p&gt;The honest summary:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Situation&lt;/th&gt;
&lt;th&gt;Usually fine&lt;/th&gt;
&lt;th&gt;Usually not&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;English and Latin-script text at normal UI size&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Chinese at normal UI size&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Text under roughly 10 px tall&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Japanese kana, Korean, Russian&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Text over a photo or gradient&lt;/td&gt;
&lt;td&gt;Sometimes&lt;/td&gt;
&lt;td&gt;Sometimes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Heavily resized screenshots&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;InSnap's local recognition handles Chinese, English and Latin-script languages well, including accented characters. It is not reliable for Japanese kana, Korean or Russian. That is a property of the bundled model, not a setting, so the honest move for those scripts is to verify anything you copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does the text recogniser tell me when it is unsure?
&lt;/h3&gt;

&lt;p&gt;No. A character classifier always returns a best guess, and the interface has no separate confidence indicator for copying. The safe assumption is that any character it returns is the most likely one, not a guaranteed one.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I fix a wrong character by running it again?
&lt;/h3&gt;

&lt;p&gt;Not usually, because the input has not changed and the model is deterministic on the same pixels. The fix is to change the input: recapture the same region at a larger size, or zoom the source before capturing, then recognise again.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why does it work on one screenshot and fail on another of the same page?
&lt;/h3&gt;

&lt;p&gt;Most often text size in pixels, which depends on the display scaling and on whether the capture was at 1x or 2x. The same page at a different zoom or on a different display can cross the size boundary.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does it read text inside images and photos?
&lt;/h3&gt;

&lt;p&gt;Only if the text is large and clear over a plain background. Text over a photo, a gradient or a complex illustration is where wrong characters most often appear.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need an internet connection for this to work?
&lt;/h3&gt;

&lt;p&gt;No. Recognition runs locally, including the copy step. Nothing is uploaded, and the accuracy is the same offline.&lt;/p&gt;

</description>
      <category>ocr</category>
      <category>productivity</category>
      <category>tutorial</category>
      <category>tools</category>
    </item>
    <item>
      <title>How to Copy Text From a Screenshot or Image on Mac and Windows</title>
      <dc:creator>Akok</dc:creator>
      <pubDate>Tue, 27 Oct 2026 16:40:13 +0000</pubDate>
      <link>https://dev.to/978190375/how-to-copy-text-from-a-screenshot-or-image-on-mac-and-windows-4po8</link>
      <guid>https://dev.to/978190375/how-to-copy-text-from-a-screenshot-or-image-on-mac-and-windows-4po8</guid>
      <description>&lt;p&gt;You have a screenshot, and you need the words inside it. OCR (optical character recognition) turns those pixels back into selectable text. On a Mac, open the image in Preview or Quick Look, drag across the words and press Command-C. On Windows 11, take a snip and use Text actions in Snipping Tool, or press Windows key + Shift + T with PowerToys installed. If you have not captured anything yet, InSnap does both at once: drag a region, click OCR on the capture toolbar, and copy.&lt;/p&gt;

&lt;p&gt;Built-in tools are free. InSnap is faster when the text is already on screen.&lt;/p&gt;

&lt;h2&gt;
  
  
  On a Mac: Live Text
&lt;/h2&gt;

&lt;p&gt;Live Text has shipped with macOS since Monterey and works in Preview, Quick Look, Photos and Safari.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Preview:&lt;/strong&gt; open the image, hover until the pointer changes, drag to select, and press Command-C. If nothing selects, use &lt;strong&gt;Tools › Text Selection&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Quick Look:&lt;/strong&gt; select the file in Finder, press Space, drag over the text, and press Command-C. The Live Text icon offers &lt;strong&gt;Copy All&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Photos:&lt;/strong&gt; open the photo and select text the same way.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Recognition runs on the Mac; available languages depend on your macOS version and region.&lt;/p&gt;

&lt;h2&gt;
  
  
  On Windows: Snipping Tool and PowerToys
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Snipping Tool (Windows 11):&lt;/strong&gt; press Windows key + Shift + S, open the snip, click &lt;strong&gt;Text actions&lt;/strong&gt;, then select words or use &lt;strong&gt;Copy all text&lt;/strong&gt;. The Windows 10 Snipping Tool lacks this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PowerToys Text Extractor:&lt;/strong&gt; a free Microsoft utility for Windows 10 (version 2004 or newer) and Windows 11. Enable it, press Windows key + Shift + T, and drag a box around the text. It uses the OCR language packs in Windows.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Copy text with InSnap, on Mac and Windows
&lt;/h2&gt;

&lt;p&gt;InSnap is a screenshot and annotation tool for macOS 14.4+ and Windows 10+. Its OCR is free, local, and works the same on both platforms.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Press Command-1 (Ctrl+1) and drag a box around the text.&lt;/li&gt;
&lt;li&gt;Click &lt;strong&gt;OCR&lt;/strong&gt; on the toolbar; recognition runs in the background while the capture stays on screen.&lt;/li&gt;
&lt;li&gt;Select text as in a document: drag across characters, click a line to select it whole, or Shift-click to add more lines. The panel beside the selection lists the same lines.&lt;/li&gt;
&lt;li&gt;Press Command-C (Ctrl+C) to copy the selection. With nothing selected, copying takes all the text, and the panel has buttons to copy the selection or everything.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuzct0zumap32vhpr4z23.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuzct0zumap32vhpr4z23.png" alt="Copying text from an image with InSnap" width="800" height="479"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Get better recognition results
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Crop tightly.&lt;/strong&gt; Select the text and little else.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Capture at full resolution.&lt;/strong&gt; A real screenshot beats a stretched copy; upscaling adds no detail.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep text horizontal.&lt;/strong&gt; A photo taken at an angle introduces skew.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid glare, shadows and moiré&lt;/strong&gt; from photographing a glossy screen.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use readable text sizes.&lt;/strong&gt; Very small text is where errors start.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7i3lzlgzj94ihhg6n4ho.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7i3lzlgzj94ihhg6n4ho.png" alt="Text recognised in a selection" width="" height=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Which languages are recognised
&lt;/h2&gt;

&lt;p&gt;InSnap reads Chinese (Simplified and Traditional), English, and Latin-script languages including German, French, Spanish, Portuguese and Italian, accents included.&lt;/p&gt;

&lt;p&gt;Japanese kanji are often recognised while kana frequently come out wrong. Korean and Russian are not reliably recognised yet. Lines mixing Chinese and English usually work; scripts the model cannot read will not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your image stays on your device
&lt;/h2&gt;

&lt;p&gt;Recognition uses a bundled model and runs on your Mac or PC. Nothing is uploaded, no account is needed, and it works offline, which matters when a screenshot holds client names or internal tickets.&lt;/p&gt;

&lt;h2&gt;
  
  
  Built-in tools vs InSnap
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Built-in tools&lt;/th&gt;
&lt;th&gt;InSnap&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;macOS&lt;/td&gt;
&lt;td&gt;Live Text in Preview, Quick Look and Photos&lt;/td&gt;
&lt;td&gt;OCR on the capture toolbar&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Windows&lt;/td&gt;
&lt;td&gt;Snipping Tool text actions (Windows 11); PowerToys (Windows 10 and 11)&lt;/td&gt;
&lt;td&gt;OCR on the capture toolbar&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Select text on the image&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes, on the image or in the panel&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Languages&lt;/td&gt;
&lt;td&gt;Depends on the OS and language packs&lt;/td&gt;
&lt;td&gt;Chinese, English and Latin-script languages&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost&lt;/td&gt;
&lt;td&gt;Included with the OS; PowerToys is free&lt;/td&gt;
&lt;td&gt;Free&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Troubleshooting
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Nothing is recognised.&lt;/strong&gt; Check that the selection contains text and is not a tiny box. Logos, handwriting and text drawn into an illustration are out of scope. Use a real screenshot, not a scaled image.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Characters come out wrong.&lt;/strong&gt; Lookalikes such as O and 0, l and 1, or rn and m, plus stylised fonts, low contrast and small sizes cause most errors. Proofread codes and amounts before pasting.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Mixed languages.&lt;/strong&gt; Select only the lines you need, with one script per selection where possible.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How do I copy text from a screenshot without extra software?
&lt;/h3&gt;

&lt;p&gt;On a Mac, use Live Text in Preview or Quick Look. On Windows 11, take a snip and use Text actions in Snipping Tool.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is OCR free in InSnap?
&lt;/h3&gt;

&lt;p&gt;Yes, with no Pro licence or account required.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which languages can InSnap's OCR read?
&lt;/h3&gt;

&lt;p&gt;Chinese (Simplified and Traditional), English, and Latin-script languages such as German, French, Spanish, Portuguese and Italian. Japanese kana, Korean and Russian are not reliably recognised.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does InSnap upload my screenshot for OCR?
&lt;/h3&gt;

&lt;p&gt;No. Recognition runs on your computer, and the image never leaves your device.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I copy only part of the recognised text?
&lt;/h3&gt;

&lt;p&gt;Yes. Drag over words on the image, click a line, or select in the panel, then copy. With nothing selected, everything is copied.&lt;/p&gt;

&lt;h3&gt;
  
  
  How do I extract text from an image on Windows 10?
&lt;/h3&gt;

&lt;p&gt;Snipping Tool text actions are only in Windows 11. On Windows 10, use PowerToys Text Extractor, or capture with InSnap and press OCR.&lt;/p&gt;

</description>
      <category>ocr</category>
    </item>
    <item>
      <title>A developer's screenshot workflow: bug reports, code review, and step guides</title>
      <dc:creator>Akok</dc:creator>
      <pubDate>Mon, 26 Oct 2026 16:45:33 +0000</pubDate>
      <link>https://dev.to/978190375/a-developers-screenshot-workflow-bug-reports-code-review-and-step-guides-2kgo</link>
      <guid>https://dev.to/978190375/a-developers-screenshot-workflow-bug-reports-code-review-and-step-guides-2kgo</guid>
      <description>&lt;h2&gt;
  
  
  Why another screenshot post
&lt;/h2&gt;

&lt;p&gt;Developers take screenshots all day: a bug report, a design review, an API example, a step in an onboarding doc. The built-in tools capture pixels; the real work starts &lt;em&gt;after&lt;/em&gt; that—annotating, redacting, stitching, writing the steps down.&lt;/p&gt;

&lt;p&gt;I build InSnap, a screenshot and screen-recording tool for macOS and Windows, so take the tool mentions with that bias. The workflow below works with any editor; InSnap just removes the app-switching.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3wti6pzy0u5t8ygjylb1.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3wti6pzy0u5t8ygjylb1.jpg" alt="Annotating a screenshot inline" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Bug reports that get fixed
&lt;/h2&gt;

&lt;p&gt;A screenshot alone tells the reader &lt;em&gt;what&lt;/em&gt; you saw, not &lt;em&gt;what you did&lt;/em&gt;. Three additions change that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Numbered steps.&lt;/strong&gt; Put 1, 2, 3 on the screenshot in the order you clicked. In InSnap, changing a number shifts the following numbers automatically, so you do not renumber by hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Arrows that point at the exact control.&lt;/strong&gt; Draw them on the capture overlay; no image editor round trip.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Redaction before sharing.&lt;/strong&gt; Solid fill for tokens and passwords, high-strength mosaic for names and emails. Blur is the weakest option—avoid it for secrets.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fluucm36df5woqqyslune.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fluucm36df5woqqyslune.jpg" alt="Numbers and arrows on the capture overlay" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Long stack traces and logs rarely fit on one screen. A scrolling screenshot stitches the whole page into one image:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8wnu05bl7cgsha5ti91c.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8wnu05bl7cgsha5ti91c.jpg" alt="Scrolling screenshot with a live preview" width="800" height="497"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Then attach a template the reader can reproduce:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;## Environment&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; OS: macOS 14.4 / Windows 11 23H2
&lt;span class="p"&gt;-&lt;/span&gt; App version: 1.2.3 (build 456)
&lt;span class="p"&gt;-&lt;/span&gt; Runtime: Node 24 / Chrome 155

&lt;span class="gu"&gt;## Steps&lt;/span&gt;
&lt;span class="p"&gt;1.&lt;/span&gt; Open Settings → Notifications
&lt;span class="p"&gt;2.&lt;/span&gt; Turn off Email alerts
&lt;span class="p"&gt;3.&lt;/span&gt; Reload the page

&lt;span class="gu"&gt;## Expected / actual&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; Expected: the toggle stays off
&lt;span class="p"&gt;-&lt;/span&gt; Actual: it turns back on after reload

&lt;span class="gu"&gt;## Attachments&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; Screenshot: above (steps 1–3)
&lt;span class="p"&gt;-&lt;/span&gt; Recording: screen-recording.mp4
&lt;span class="p"&gt;-&lt;/span&gt; Console log: long screenshot
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  2. Code review and before/after
&lt;/h2&gt;

&lt;p&gt;For UI changes, a before/after pair is faster to review than a paragraph. Capture both states, stitch them in the image editor, and paste the result into the PR.&lt;/p&gt;

&lt;p&gt;When I need to &lt;em&gt;use&lt;/em&gt; a screenshot while coding—a design spec, an API response, a config snippet—I pin it above other windows instead of switching tabs. Pinning a clipboard text or JSON also works: it renders as a readable card, not an image of text.&lt;/p&gt;

&lt;p&gt;Share links are useful when the attachment would expire in chat. In InSnap that is the optional Cloud subscription (expiry and optional password); a saved file attached to the PR is enough for local teams. Pro and Cloud are separate; neither includes the other.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Docs and debugging
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Copy text from an image.&lt;/strong&gt; Box the error, hit OCR, then select text directly on the image. Recognition runs locally—no upload—and works well for Chinese, English and Latin-script languages. Japanese kana, Korean and Russian are not reliable yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep a command or JSON beside the code.&lt;/strong&gt; Pin the clipboard: plain text, Markdown and HTML become a floating card.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Find that screenshot from last week.&lt;/strong&gt; History keeps captures locally and indexes OCR text, so searching an error code finds the image even if the file name is meaningless.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgt170vn1tuv0i0k6iszl.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgt170vn1tuv0i0k6iszl.jpg" alt="OCR: select text directly on the screenshot" width="800" height="502"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvkjsw21ybuifmh0gc88b.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvkjsw21ybuifmh0gc88b.jpg" alt="Searchable screenshot history with tags and OCR text" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Turn a task into a guide
&lt;/h2&gt;

&lt;p&gt;Recording a task is often faster than writing the steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start guide recording.&lt;/li&gt;
&lt;li&gt;Do the task normally. Every click becomes a step: a screenshot taken &lt;em&gt;before&lt;/em&gt; the click, a marker on the target, and a title derived from the button or input name. Double clicks merge; drags are ignored.&lt;/li&gt;
&lt;li&gt;Stop. The guide opens in an editor.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In the editor you can rewrite titles, reorder or hide steps, add substeps and callouts (tip/warning/note), crop each screenshot, and blur the same region across &lt;strong&gt;all&lt;/strong&gt; steps in one action.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgnjka35i2slc9a5ib2ee.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgnjka35i2slc9a5ib2ee.jpg" alt="Guide editor: steps on the left, screenshot in the middle, annotation tools on the right" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Export matters more than editing: PDF for customers, Word for colleagues, PowerPoint for training, HTML for a knowledge base, Markdown for a repo, SCORM for an LMS, JSON for automation.&lt;/p&gt;

&lt;p&gt;For screen recordings, the same idea applies to video. “Record &amp;amp; edit” stores mouse and keyboard events; the editor generates zoom segments around clicks and follows the cursor between them. You can delete or add segments on the timeline instead of keyframing by hand.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhgjykyvynfqe0pyk0c5q.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhgjykyvynfqe0pyk0c5q.jpg" alt="Video editor with generated zoom segments" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  5. My setup
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Action&lt;/th&gt;
&lt;th&gt;macOS&lt;/th&gt;
&lt;th&gt;Windows&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Capture&lt;/td&gt;
&lt;td&gt;&lt;code&gt;⌘1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Ctrl+1&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pin clipboard&lt;/td&gt;
&lt;td&gt;&lt;code&gt;⌘2&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Ctrl+2&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Other actions (long screenshot, recording, guides, history) are optional global hotkeys. Inside the capture overlay, &lt;code&gt;⌘A&lt;/code&gt; selects the full screen, &lt;code&gt;⌘C&lt;/code&gt; copies, &lt;code&gt;⌘S&lt;/code&gt; saves, &lt;code&gt;⌘Z&lt;/code&gt; undoes.&lt;/p&gt;

&lt;p&gt;Settings worth turning on:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;auto-detect windows and UI elements (hover instead of dragging edges);&lt;/li&gt;
&lt;li&gt;screenshot history with OCR indexing;&lt;/li&gt;
&lt;li&gt;output options: scale Retina captures to 1x and add a 1px border for docs.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  6. Limits, honestly
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No Linux build.&lt;/strong&gt; macOS 14.4+ and Windows 10+ only.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OCR is local and language-limited.&lt;/strong&gt; Chinese, English and Latin-script languages are good; Japanese kana, Korean and Russian are weak.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Smart erase is a local algorithm, not a generative model.&lt;/strong&gt; It works best on flat, gradient and UI backgrounds; subjects that match the background color can leave artifacts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pro and Cloud are separate.&lt;/strong&gt; Pro unlocks advanced tools (long screenshots, GIF, video effects, guides, smart erase); Cloud is an optional subscription for hosted share links. Neither includes the other.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Screenshots, annotation, pinning, OCR and history are free&lt;/strong&gt;, including basic MP4 recording.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;If your current loop is &lt;em&gt;system screenshot → open Preview → draw arrow → send in chat → open a recorder for the video&lt;/em&gt;, collapsing it into one tool saves a surprising amount of context switching.&lt;/p&gt;

&lt;p&gt;InSnap runs on Mac and Windows: &lt;a href="https://insnap.app" rel="noopener noreferrer"&gt;https://insnap.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I build InSnap. The workflow above is what I use for my own bug reports and docs; the tool is optional.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>softwaredevelopment</category>
      <category>tools</category>
      <category>devtools</category>
    </item>
  </channel>
</rss>
