# 1ShowcaseTool — full published content > 9 articles. Source: https://1showcasetool.com --- ## A countdown you can walk through Source: https://1showcasetool.com/blog/a-countdown-you-can-walk-through Published: 2026-09-01 Tags: screen recording, recording, camera, macos, workflow Press record and the app steps aside — a click-through 3-2-1 counts down on every screen while you get to the window you actually meant to capture. You line up the window you want to show, press record, and then spend the first three seconds of the take watching your recording app count down over its own interface. By the time the 3-2-1 clears, you're still clicking your way back to the thing you actually meant to demo — and that fumble is now baked into the footage. Recording your entire screen only made it worse: the countdown opened on top of the app, so the opening frames were never the window you cared about at all. The gap between "press record" and "be ready" has always been the most awkward part of screen recording. You either pad the front of every take with dead air and trim it later, or you accept that the first few seconds are throwaway. ## What changed You can now start a recording and use the countdown to get where you need to be. Press Start and 1ShowcaseTool hides itself, then a click-through 3-2-1 appears on every display — restating exactly what's about to be recorded — while you walk to the window you actually want on camera. A full-screen take never opens on the app counting down over its own window again. Three changes in this release work together to close that "am I really recording the right thing?" gap: the countdown moves out of the app, the recording bar tells you what's live, and the camera does the framing work so the edit is half-finished before you stop. ## How it works in practice ### The countdown gets out of your way When you press Start on a screen recording, the app disappears and a 3-2-1 overlay appears on every screen, click-through so it never blocks what's underneath. It restates what you picked — a display, a window, a region — so you can confirm at a glance instead of trusting your memory of which button you hit. Those three seconds are now useful time: you spend them clicking into the window you want to open on, not watching an app animate. Change your mind mid-count? Press Cancel or hit Esc and the take is scrapped before a single frame is written. Navigate away from the Record screen entirely and the countdown stops on its own, so a recording never quietly starts on a screen you've already left. If you're recording 1ShowcaseTool itself, the app shows itself back before the countdown helper starts — so a self-recording opens on a real frame of the app instead of an empty black one. ### While you're recording, the bar shows what's actually live Once the take starts, the floating recording bar carries a live camera thumbnail alongside on/off pips for your microphone and system audio. It answers the question every screen recorder has asked mid-take: *is this actually capturing what I think it is?* You can see your camera is framed and your mic is hot without stopping to check. Everything in the bar stays out of the recording — it's click-through except for the pill itself — so watching your own status never leaks into the footage. ### The camera has already done the framing By the time you stop, the editor has a head start. The automatic camera now zooms on cursor *dwells*, not just clicks — a pause where you're clearly pointing something out pulls the view in. It holds a beat longer over an open dropdown so the menu stays on screen while the camera is pushed in, and it ignores text-selection drags, so highlighting a paragraph no longer drags the crop across the page. A portrait or already-tight recording is left at 1×, because pushing in on it would only make it unreadable. You can also keep the camera glued to your pointer: flip on **Follow the pointer** in the Camera panel and, while zoomed in, the crop tracks your cursor through a dead-zone of the visible frame and settles when you stop. A control the camera just pushed in on won't drift off screen the moment you reach for the next one. If you record with a talking-head bubble, the new **Shrink with zoom** toggle lets it yield to whatever the camera pushed in on while keeping its anchor corner in place. ![The 1ShowcaseTool editor with the Ask the studio AI assistant open running a natural-language "zoom in on the click" edit, alongside the Frame and Camera panels and a timeline of camera-zoom cues](https://assets.stoicsoft.com/posts/1showcasetool/v1.8.0/ai-video-editor.jpg) ### The library keeps up too The recording tiles were redesigned so the poster stays the loudest thing on each card: the quiet facts — steps, when, where it was recorded from — now sit in a single line, and coloured chips are reserved for what's only true of *some* recordings. A wider column gives the poster room to tell five different takes all called "Entire screen" apart. Hover any recording and the reveal-in-Finder and delete buttons appear on the tile itself, matching what the list view already offered. Each screen recording's tile also shows how many days are left before its raw footage is swept off disk — raw footage is kept exactly as recorded, unredacted, so it isn't held forever. The chip turns amber as the deadline nears, so you know to export or ignore it in time; once the sweep runs it reads "footage expired" instead of the button silently vanishing. Your step screenshots are always kept — the countdown is only ever about the raw video. ## Before vs after | Starting a take | Before v1.8.0 | Now | | --- | --- | --- | | Press record | Countdown animates inside the app window | App hides; countdown floats on every screen | | Full-screen recording | First seconds capture the app counting down over itself | Opens on the window you walked to | | Getting to your target window | Happens *after* recording starts — on camera | Happens *during* the countdown — off camera | | Confirming mic / camera / audio | Stop and check, or hope | Live thumbnail and pips in the floating bar | | Framing the important moments | Zoom in by hand, clip by clip | Auto-camera on dwells and clicks; optional pointer-follow | ## Who benefits most **Anyone recording their whole screen.** This is the take that used to be unusable — the one that opened on the app instead of your desktop. It now opens where you point it. **People who record without a second monitor.** When the app, the countdown, and your target window all share one screen, getting the app out of the way during the count is the difference between a clean start and a re-take. **Demo and tutorial makers.** The auto-camera doing the dwell-and-zoom work means the raw take arrives already framed around the moments that mattered, so the edit is trimming rather than building from scratch. ## Try it Update to v1.8.0, pick a window or a whole display, and press Start — then use the three seconds to get where you want to open. The take that begins is the one you meant to record, framed for you, with nothing of the app in the opening frame. The whole app has moved to cinema black while you were at it, so the editor gets out of the way of your footage too. --- ## From raw capture to a shot worth sharing — v1.7.0 adds a Screenshot studio Source: https://1showcasetool.com/blog/screenshots-beautified Published: 2026-08-25 Tags: release, v1.7.0, screenshots, gif, editing Capture a window, display or region, drop it on a background inside a device frame, animate it and export a PNG, GIF or APNG — all in one place, all on your machine. Plus a waveform, pause and clap detection, and faster MP4 exports in the recording editor. You take a screenshot to show someone something — a bug, a setting, a result you're proud of — and it lands in your downloads folder as a bare rectangle of pixels. That's fine for a quick "see?" in a chat. But the moment the shot has to go somewhere public — a changelog, a landing page, a social post, a help doc — it looks like exactly what it is: an unedited grab. So you open a separate design app, drop it on a background, round the corners, maybe stand it in a phone frame, blur out the one line you forgot was sensitive, and export a PNG. If you want it to move, you start over in yet another tool to make a GIF. Four apps and twenty minutes for one image. And every one of those hops is a place your original, un-redacted capture can leak — uploaded to a web beautifier, synced to a cloud editor, or just left sitting in a temp folder. ## One studio, from capture to shareable v1.7.0 adds a **Screenshot studio** to 1ShowcaseTool, so the whole trip — capture, beautify, animate, redact, export — happens in one place, on your machine. You turn a raw grab into a designed image, still or animated, and nothing leaves your computer unless you send it. ![The new Screenshots library in 1ShowcaseTool showing a grid of captured window, display and region shots with their dimensions and capture type, next to New screenshot, From clipboard and Import image actions](https://assets.stoicsoft.com/posts/1showcasetool/v1.7.0/screenshot-library.jpg) ## How it works in practice ### Capture exactly what you mean to The **New screenshot** button opens a menu of **Capture area**, **Capture fullscreen** and **Capture window**, each showing its own keyboard shortcut, so the shot you want is one click — or one keystroke — away. You can also turn an image already on your **clipboard** into a shot, or import a PNG, JPEG or WebP you already have. Two touches make the capture itself cleaner. Before a display or region capture, the app **steps out of its own shot** — 1ShowcaseTool hides its window, so it's never sitting in the picture you take. And a **menu-bar icon plus global shortcuts** let you grab a shot without bringing the app forward first; every shortcut is rebindable in **Settings → Shortcuts**, and a small preview card appears in the corner afterward so you can jump straight into editing or saving before it fades on its own. Every capture lands in its own library, kept apart from your recordings and guides. ### Make it look designed Drop the shot on a **gradient, a wallpaper, a blurred version of itself, or a plain colour**. Set the padding, the corner rounding, the shadow softness and the aspect ratio. Stand it inside a **device frame — phone, tablet, laptop or browser chrome** — in one of five finishes. Then, if the image needs a voice, add a **meme bar** with top and bottom captions, a **quote card**, or a cartoon **pet** peeking over the frame, and mark it up with the same annotation toolset as the rest of the app: arrows, boxes, text, numbered counters, pencil, highlighter and spotlight. The editor **saves as you work**, so closing a shot and reopening it later brings back exactly what you left. ### Bring it to life A new **Motion** tab animates the shot with a **camera move** — push-in, pan, drift or Ken-Burns — and a **particle layer** — sparkle, confetti, hearts, snow or dust — at 8, 12 or 16 frames a second. A **live preview** plays the loop right in the panel, so you tune the move and the sparkle and see the result immediately, with nothing to export first. ![The Screenshot editor's Motion tab animating a shot inside a device frame, with camera-move and particle controls and a cartoon pet in the corner, and PNG, WebP, GIF and APNG export options in the sidebar](https://assets.stoicsoft.com/posts/1showcasetool/v1.7.0/screenshot-motion-tab.jpg) ### Export it the way you need it Save a **PNG** or **WebP** still, or — with Motion on — an animated **GIF or APNG** that matches the preview frame for frame. The GIFs come out **smooth, without the colour banding they're known for**, and APNG keeps full colour and crispness where it's supported. Or skip the file entirely: **copy** the composed image to your clipboard, **pin** it above every other window, **drag** it straight into another app, or hand it to another device over a **self-destructing LAN link** with an optional password and expiry — one that dies when the app closes. ### Nothing private, by accident Redacting a screenshot is destructive, not decorative. Cover a region and it's burned into the exported image — an opaque fill, or a **Secure pixelate** that scrambles the pixels underneath, not a blur you could sharpen back. The exported file is the copy that carries the redaction, so it's the PNG you hand out — never a browser upload of the raw grab. And only the composed image ever leaves the app: never the original capture, and only when you choose to copy, save, export or share it. ## Before vs after | Getting one shareable screenshot | Before v1.7.0 | With the Screenshot studio | | --- | --- | --- | | Capture | the OS grab tool | area, fullscreen or window — from the app or the menu bar | | Beautify | a separate design app | backgrounds, device frames, padding and shadow in-app | | Redact | blur in an image editor (reversible) | an opaque fill or Secure pixelate burned into the export | | Animate | a second GIF tool | the Motion tab, with a live preview | | Export | usually a PNG per tool | PNG, WebP, GIF or APNG — plus clipboard, pin, drag, LAN share | | Where your pixels go | uploaded and synced across apps | never leave your machine | ## Your recording editor can hear now The screen-recording editor picks up three upgrades in the same release. Its timeline now draws your recorded soundtrack as a **waveform**, so you can see where you spoke and where you went quiet at a glance. A new **Sound** panel scans the take for **pauses** and marks them — seek to one and cut it with a keystroke, or press **Cut** — and because typing and clicks count as activity, a busy-but-quiet stretch is never mistaken for silence. It also finds **claps, snaps and bright beeps**, so a hand-clap you made while recording becomes a spot you can jump straight to (these markers are editing aids only — they never show up in the exported video). Editing got faster too. **Shift-click a range or ⌘/Ctrl-click** to select several clips and delete them in one step, and a **Merge** button recombines clips you split — joining only neighbouring pieces that still touch and play at the same speed, with a plain-language reason when they can't. And exports run quicker: the editor now asks your machine for a **hardware encoder** and overlaps each frame's work, so a long take renders meaningfully faster while the file stays identical to the pixel. ## Who gets the most out of it - **Anyone who ships in public.** Changelogs, docs, landing pages, launch posts — a designed screenshot now comes out of the same tool, with no detour through a browser beautifier. - **People who handle sensitive screens.** Support, security and finance teams get one place to capture and permanently mask, with no un-redacted original travelling between apps to be forgotten. - **Makers of tutorials and demos.** The animated GIF or APNG turns a static step into something that moves, and the recording editor's new ears make cutting dead air quick. ## Try it The Screenshot studio — every background, finish, device frame, meme bar, quote, annotation, motion and export format, and all masking — is **free**. Pro unlocks the full set of pets and removes the small corner watermark. Update to v1.7.0 and take your next screenshot inside the app that already keeps your recordings honest. --- ## Point at what matters — v1.6.0 lets you draw right on your screen recording Source: https://1showcasetool.com/blog/draw-on-your-recording Published: 2026-08-23 Tags: release, v1.6.0, annotations, screen recording, editing A new Annotate panel draws arrows, boxes, text and spotlights straight onto your screen recording and burns them into the MP4 — plus Clip view to edit one clip up close, and .1showcase project files you can save, open and hand off. You finish the recording, watch it back, and realize the moment that matters is one small button in the top-right corner. So you do what everyone does: you talk over it. "See that little icon up there? No, the other one." Or you drop the file into a separate image or video editor, draw an arrow, export again, and hope you lined it up with the right frame. The recording was already the demo — but the thing you actually wanted to point at was still trapped in your narration. ## What changed v1.6.0 adds an **Annotate** panel to the screen-recording editor, so you can draw arrows, boxes, text and spotlights directly on the picture and burn them into the exported MP4. The mark you draw is the mark your viewer sees — no second tool, no re-export dance. Alongside it, the release makes two quieter but far-reaching changes: you can now zoom the timeline into a **single clip** to edit it up close, and every recording is now a real **`.1showcase` file** you can save, reveal, double-click and hand to someone else. ![The Annotate panel open in the 1ShowcaseTool editor with arrow, rectangle, text and spotlight tools and controls for colour, stroke and opacity, with red arrows and a boxed callout drawn straight onto a screen recording](https://assets.stoicsoft.com/posts/1showcasetool/v1.6.0/annotate-panel.jpg) ## How it works in practice ### Draw the mark, don't describe it Open the **Annotate** panel (press `N`) and you get a full drawing kit that lives right on the film: **Arrow, Rectangle, Ellipse, Line, Text, Counter** badges, a freehand **Pencil**, a **Highlighter**, and a **Spotlight** that dims everything except the region you care about. Drag on the picture to place a mark; press `Esc` to finish. Every mark is burned into the export at full resolution, so it survives into the MP4 exactly as you drew it. Marks are for pointing, not hiding. If something needs to be covered — an account ID, an API key — masking is still the tool for that, because a mask destroys the pixels underneath. An arrow drawn on top of a secret is still sitting on top of a secret. ### Time each mark, and pin it where it belongs A mark doesn't have to be on screen for the whole take. Just like a mask, you give each one a moment: use **from here** and **to here** so an arrow appears exactly when you click the button and fades once you've moved on. Then decide what the mark should hold onto. The **Anchor** control has two settings: **Follows the screen** makes the mark zoom and tilt along with the recording and any posed device, so an arrow stays glued to a button even as the shot pushes in; **Sits on the frame** keeps it fixed like a title card, no matter what the footage does underneath. Text and counters default to the frame; arrows, boxes and the spotlight default to the screen — which is almost always what you want. Everyone can draw every mark, time it, and place it — that's free and never blocked. A Pro licence unlocks the *styling*: your own colours, the choice of typeface, and the seven text styles. Without it, marks simply render in the default colour and type. ### Zoom into one clip without losing your place A long recording is really a stack of clips, and until now you edited them all against one crowded timeline. v1.6.0 adds **Clip view**: pick a clip from the **Show in timeline** menu — or just click the clip — and the timeline zooms down to that one piece so you can work on it up close. **Exit clip view** (or press `Esc`) drops you back to the whole take. The important part is what *doesn't* move: the lanes keep the take's own clock, so a mark you timed, a camera move you set, or a mask you placed all stay exactly where they belong as you step into a clip and back out. You get the focus of editing one piece without the risk of knocking everything else out of sync. ![The editor's Show in timeline menu listing a recording's clips — Whole take plus Clip 1 through Clip 6 — the pieces you can now zoom into one at a time](https://assets.stoicsoft.com/posts/1showcasetool/v1.6.0/clip-view-timeline.jpg) Inside a clip you still get its own scene and camera; Clip view just gives you the room to see them. ![Clip view zoomed into a single clip, its Frame panel showing that this clip carries its own scene and camera while everything else follows the take](https://assets.stoicsoft.com/posts/1showcasetool/v1.6.0/clip-view-detail.jpg) ### Treat every recording as a file you own Until now a recording lived inside the app and nowhere else. In v1.6.0 every recording is a **`.1showcase` file** on disk — with its screenshots, editable sidecars and studio settings inside it — saved by default to **`~/Documents/1ShowcaseTool`**, a folder you can move wherever you like. There's a real **File** menu to match: **Open Project…** (`⌘O`), **Open Recent**, **Save Project** (`⌘S`), and **Reveal Project File** to jump straight to it in Finder. **Double-click** a `.1showcase` in Finder, or drag it onto the app, and it opens right up. If your library already holds that project, it just opens that recording instead of quietly making a duplicate — so passing a project to a teammate, or moving your work to another machine, finally behaves the way files are supposed to. ### Rename by clicking the name A smaller thing you'll feel every day: **click a recording's title** — in the library or in the editor — and type the new name in place. No dialog, no menu. Eight takes all called "Entire screen" become eight takes with real names in a few seconds. ## Before vs After | Pointing something out | Before v1.6.0 | With v1.6.0 | |---|---|---| | Highlight a button in the demo | Narrate "see that icon?" or round-trip through a separate editor | Draw an arrow on the film, timed to the click | | Focus attention on one area | Hope the viewer's eye lands in the right place | Drop a spotlight and dim the rest | | Edit one clip closely | Squint at it inside the full timeline | Zoom into it with Clip view, everything else held in place | | Move a recording to another machine | No file to move | Save the `.1showcase` and open it anywhere | | Rename a take | — | Click the title and type | ## Who benefits most **Developers writing setup guides** get to point at the exact field in a config screen instead of describing where it is — and keep the redaction discipline intact, because marks and masks are still two different tools. **Anyone recording a product walkthrough** can spotlight the one control that matters in a busy UI, so a viewer never has to hunt for what you're talking about. **People handing work off** finally have something to hand off: a single `.1showcase` file that carries the whole recording, ready to open on another machine or by another person. ## The rest of v1.6.0 **Find silence** got smarter about what counts as "doing something". Typing now registers as activity alongside clicks, so its suggested trims land in the genuinely idle gaps between your actions rather than cutting across a stretch where you were quietly typing. That also fixes a sharp edge: a long, busy-but-quiet recording made without narration could previously have Find silence offer to delete almost the whole thing. Typing and clicks are now protected, and a silence cut is split around every action instead of swallowing it. ## Try it Update to v1.6.0, open a recording, and press `N`. Draw one arrow on the moment that matters, time it to the click, and export. The thing you used to point at with your voice is now on the screen — and the file it lives in is yours to keep. --- ## Put yourself in the demo — v1.5.0 lands the talking-head overlay Source: https://1showcasetool.com/blog/talking-head-overlay Published: 2026-08-22 Tags: release, v1.5.0, talking head, camera, screen recording Record your camera alongside the screen and lay your face over the demo as a separate overlay — one that plays in sync with the screen, stays locked to your voice, and rides into the exported MP4, with a redesigned panel to position, shape and mirror it. A screen recording is a faceless thing. It shows exactly what you did, click by click, and none of who was doing it. For a bug repro that's fine — but for a product walkthrough, an onboarding video, or a demo you want someone to actually trust, the missing piece is you. You recorded your camera alongside the screen for exactly that reason, switched on the overlay in the editor, and… nothing showed. Or your face lagged a beat behind your voice, or it froze on one frame while the demo played on without you. ## What changed v1.5.0 makes the **talking head** real. Record your camera alongside the screen, switch on the camera track in the editor, and your face rides over the demo as a separate overlay — one that plays in sync with the screen, stays locked to your voice, and follows into the exported MP4. A redesigned panel lets you place and shape the bubble exactly where you want it. And the failures that made the feature unreliable — the track that never appeared, the lips that ran ahead of the audio, the overlay that froze — are fixed. ![The editor's Frame panel with the Talking head section switched on — "Show the camera track: a separate track, never baked into the screen" — and the camera bubble resting in the corner of the recording](https://assets.stoicsoft.com/posts/1showcasetool/v1.6.0/clip-view-detail.jpg) ## How it works in practice ### Record with the camera on Turn **Camera** on before you record, and 1ShowcaseTool captures your webcam alongside the screen. Nothing about your demo changes — you're still recording the same window — but now there's a camera track riding along with it, ready to use later or leave off entirely. ### Switch on the camera track — as a layer, not a burn-in In the editor, enable the camera track and your face appears over the demo as a **separate overlay that is never drawn into the screen itself**. That separation is the whole point: the recording underneath stays clean, so you can reposition, reshape, or remove the bubble at any time without touching a single pixel of the actual demo. If a take was recorded with no camera, the panel now tells you so and points you to the record screen — instead of a switch that quietly did nothing. ### Position and shape the bubble The redesigned panel gives you real control over how the talking head looks: - Drop it anywhere on a **3×3 placement grid** — corner, edge, or center. - Choose a crop: **Square, Horizontal, Vertical, or Original**. - Pick a shape: **Rounded** or **Circle**. - Set its **size**, and **Mirror** it left-to-right so your on-screen self faces the way you expect. The result is a presenter bubble that fits the composition instead of fighting it. ### It plays with the demo, and stays locked to your voice The talking head plays, pauses and scrubs **together with the screen** in the editor — step through the demo and your face steps with it — and it rides along into the exported MP4. Under the hood, its timing is measured from the recording itself, so the face matches the audio across a long take and through every pause, instead of drifting ahead or behind. The lips match the voice, start to finish. ![The talking-head bubble riding over the demo while the timeline plays, the camera track staying in sync with the screen it sits on](https://assets.stoicsoft.com/posts/1showcasetool/v1.6.0/clip-view-timeline.jpg) ## Before vs After | | Before v1.5.0 | With v1.5.0 | |---|---|---| | Your recorded camera | Often dropped — the take showed "no camera" | Found and shown, in the editor and the export | | Face vs. voice | Lips ran ahead of or behind the audio | Locked to the recording clock, in sync throughout | | During playback | Overlay could freeze on a single frame | Plays, pauses and scrubs with the screen | | Placement | — | 3×3 grid, crop, shape, size and mirror | | The demo underneath | — | Untouched — the overlay is a layer, never baked in | ## Who benefits most **Anyone recording a walkthrough or onboarding video** gets to put a face to the instructions, which is the difference between a clip that feels like documentation and one that feels like a person showing you around. **Founders and creators shipping product demos** can add presence without a separate video editor — record once with the camera on, place the bubble, export. **Anyone who tried the camera track before and gave up on it** should try again: the take that used to report "no camera" now finds that footage on its own, even if it was recorded before this release. ## The rest of v1.5.0 Most of this release was about making the talking head trustworthy. Camera footage that was being silently dropped is now found and displayed, in both the editor and the exported MP4 — and that recovery applies retroactively, so an older take recorded with the camera on shows its footage automatically. The audio-sync fix aligns the overlay to the recording clock so your voice and face stay together, and the freezing bug is gone: the face now advances with the screen instead of sitting on one frame. ## Try it Update to v1.5.0, record a short demo with **Camera** on, and switch on the camera track in the editor. Drop your face in a corner, round it off, and scrub the timeline — you'll see yourself move with the demo, in step with your own voice. The recording finally has a presenter, and the demo underneath never had to change. --- ## Stop exporting soft demos — v1.4.0 keeps your recording's own pixels Source: https://1showcasetool.com/blog/export-at-native-resolution Published: 2026-08-21 Tags: release, v1.4.0, export, resolution, screen recording A new Native resolution exports your recording at the detail you captured instead of a downscaled 1080p, the dialog states your machine's real encoder ceiling, and the preview finally fits the frame — plus OCR mask suggestions and git-synced guides. You recorded on a Retina screen, where every line of code and every label is razor sharp. Then you exported, opened the file, and the text was soft — legible if you squinted, but nowhere near what you'd captured. Somewhere between the recording and the MP4, most of your detail got thrown away to hit 1080p, and there was no setting that said so. The demo that looked crisp while you edited it shipped blurry. v1.4.0 fixes the export where it was quietly losing your pixels, and while it's there, it stops the preview from lying to you about what the frame will look like — plus three more things that keep a guide honest after you've moved on from it. ## What changed Exports now keep the resolution you actually recorded. A new **Native** setting frames the video at the recording's own pixels instead of downscaling to a default 1080p, so a Retina capture exports at the detail you captured. And when your machine can't encode that large, the dialog tells you the real ceiling before you commit — no more silent downscale. ## How it works in practice ### Export at the resolution you recorded ![The 1ShowcaseTool export dialog with resolution chips reading Native, 4K, 1440p, 1080p and 720p, with Native selected and the helper text "Uses the source canvas size", over a razor-sharp recording of an app dashboard](https://assets.stoicsoft.com/posts/1showcasetool/export-at-native-resolution/featured.jpg) The resolution list now reads **Native · 4K · 1440p · 1080p · 720p**, and new takes default to Native — which frames the video at the recording's own size rather than a fixed target. A take you already saved keeps whatever resolution it had, so nothing you finished changes underneath you. The other half of this is honesty about limits. Every machine has an encoder ceiling, and before, hitting it just meant a quietly smaller file. Now the export dialog states it outright — something like *"Native would be 5466×3226; this machine encodes up to 4096×2304, so the file is 4096×2304."* The size estimate and the preview use that same number, so what you see is what you get. ### A preview that fits instead of stretches A flat recording used to get squashed vertically in the editor whenever the inspector and timeline claimed their space — so you were grading and framing against a distorted picture. Now the preview is fit to the available frame and re-fits whenever you change resolution, aspect, padding, or background. A plain take also renders through the same picture path the posed stage uses, so the recording's UI text stays legible while you edit, not just after you export. ### Let the app find the secrets you'd miss (macOS) On a desktop-window recording there's no page to redact automatically — so v1.4.0 adds **Suggest masks with OCR**. A local, on-device scan reads the text baked into your screenshots and queues suggested mask boxes over anything that looks like a secret, for you to review and commit. It runs on Apple Vision, so it's macOS-only for now, and it says so plainly when a machine can't run it. Two guarantees matter here: the recognized text never leaves the app's core — only proposed rectangles reach your review queue — and nothing is redacted for you. A suggestion is a box you still have to look at and commit, and a committed mask is the same opaque, permanent fill as any other. ### Keep a guide in sync with the code it documents A standalone guide can now be tied to the source it describes. **Attach a Git repository**, map each step to the repository-relative files it documents, and press **Check now** to compare the guide's baseline commit against your current checkout — it flags the steps whose mapped files were changed, renamed, or deleted. **Rebaseline** accepts the current commit as the new comparison point once you've caught up; **Detach** removes the link. The repository's content is never sent to a model or over the network by this workflow — the check is a local diff of file paths, not a code upload. ## Before vs After | Shipping a demo | Before v1.4.0 | With v1.4.0 | |---|---|---| | A Retina recording | Downscaled to 1080p, soft | Native resolution, full detail | | Hitting the encoder ceiling | Silent smaller file | Dialog states the exact ceiling first | | The editor preview | Squashed flat takes | Fit to frame, re-fits on every change | | Secrets in a window capture | Find every one by eye | OCR queues suggestions to review | | A guide vs. the code it documents | Drifts silently | Check now flags every changed source file | ## Who benefits most **Anyone recording on a high-DPI display.** Native resolution is the difference between a demo that looks as sharp as your screen and one that looks like a compressed reupload. **People redacting desktop captures.** OCR mask suggestions catch the API key or email you'd have scrolled past — while still leaving every commit in your hands. **Engineers who write guides next to a codebase.** A guide tied to its repo tells you which steps went stale the moment a file it depends on changed, instead of a reader finding out for you. ## The rest of v1.4.0 Beyond exports, this release makes a whole library easier to keep accurate. A new **Needs attention** filter gathers, in one place, guides with fragile or broken anchors, screenshots waiting for review, checks gone stale, and repository drift — with status pills right on the guide cards. **Portable, editable project bundles** let you save selected recordings and guides, with their screenshots and settings, into a single `.1showcase` file to back up or move to another machine; importing remaps IDs so it never overwrites work you already have. Offline **transcription now runs on Windows and Linux too**, using an already-installed Whisper tool with networking disabled — 1ShowcaseTool downloads nothing. And you can now add your own **never-record rules** by window title, on top of the built-in credential-app blocklist, checked before any capture starts. ## Try it Open your sharpest recording, set the export to **Native**, and put the old 1080p export next to it — the difference is the detail you recorded all along. In v1.4.0, the demo ships at the resolution you saw, and the guide keeps telling you the truth long after you've moved on to the next thing. --- ## Edit the guide you generated — v1.3.0 makes every surface editable Source: https://1showcasetool.com/blog/edit-your-generated-guide Published: 2026-08-16 Tags: release, v1.3.0, guides, editing, screen recording In v1.3.0, the parts of your demo that used to be baked in at generation time are yours to change: rewrite steps in place, move the marks on the picture, reshape redaction boxes, and walk all the way around your device. You recorded the flow, generated the guide, and then read it back and found the one line that's wrong. A step title that doesn't quite say what the reader does. A callout pointing a beat to the left of the button. A device angle that shows off the app but hides the toolbar. Until now, fixing any of that meant starting over — re-record the take, regenerate the guide, and hope the new pass didn't break the two things that were already right. That's the tax v1.3.0 removes. Every surface that used to be baked in at generation time is now something you can grab and change in place — the words, the marks on each screenshot, the redaction boxes you queued, and the camera that circles your device. Nothing regenerates behind your back, and nothing you already reviewed gets reopened. ## What changed You can now edit a generated guide directly in the preview — rewrite its steps, move and retype the marks on the picture, reshape the redaction boxes before you burn them, and turn the recording on a device you can walk all the way around. The guide you generated is now a draft you own, not a printout you have to reprint. ## How it works in practice ### Rewrite a step without re-recording Open a generated guide and press **Edit steps**. The step title becomes an input, and the "what the reader should do" and "why this step matters" fields become text areas you edit right in the preview. Your changes save as you type and are flushed before any export, so what you see is what ships. The important part is what *doesn't* change. The selectors, the URL patterns, and the screenshots stay exactly as recorded — so a browser guide still replays and still points a follower at the right target after you've rewritten every word around it. You're editing the narration, not re-cutting the recording. ### Grab the marks on the picture The arrows, boxes, and badge numbers on each screenshot used to be fixed the moment they were drawn. Now you click a mark to move it, drag any of its eight handles to resize it, pull an arrow's tip and tail independently, drag its label into a clearer spot, or retype a badge number or callout. There's no mode to enter first — the marks are live on the picture, and the redacted original underneath is never rewritten while you rearrange what sits on top of it. ### Walk all the way around your device ![The 1ShowcaseTool studio editor showing a screen recording posed on a laptop turned to a three-quarter angle on a lit stage, with a Finish panel of screen-reflection, ambient-glow, film-grain and depth-of-field sliders on the right](https://assets.stoicsoft.com/posts/1showcasetool/edit-your-generated-guide/featured.jpg) The device your recording sits in is real geometry now — a body with thickness, a hinge, and depth, instead of a flat panel with a gradient painted on it. That means the camera can actually go somewhere: the pose turns a full 360° and tilts up to 85°, so a shot from the side of the deck or from above it is a real framing rather than the steepest angle the old flat panel would allow. Four new b-roll moves — Spiral up, Tilt up, Top down and Profile pass — cover the cuts, and a floor reflection and per-model finishes (Graphite, Silver, Midnight, Starlight, Charcoal, Slate) put the device on a stage instead of a swatch. A **Finish** panel gives you the last ten percent: screen reflection, ambient glow, film grain, depth of field and a touch of handheld drift, each with its own strength, plus a Lighting mood that follows the device on Auto. None of it touches which pixels ship — it changes how the take looks, not what's in the frame, so the review gate stays shut. ### Reshape the redaction boxes before you burn them The boxes you queue over secrets are editable right up until you commit them. Drag the body to move one, pull a corner handle to resize, drag a rail row to reorder, or nudge a selected box with the arrow keys (hold Shift for 10-pixel jumps). Past about 150% a 4× loupe with a crosshair follows the pointer so you can place an edge precisely, and **Preview result** paints the queue as the solid fill that will actually ship — so you check your coverage while there's still a way back. And the queue finally survives the trip out to the video and back, exactly as the hint always promised. ## Before vs After | Fixing a small mistake | Before v1.3.0 | With v1.3.0 | |---|---|---| | A wrong step title or unclear instruction | Re-record and regenerate the whole guide | Press Edit steps, rewrite it in place, autosaved | | A callout pointing at the wrong spot | Live with it or start over | Drag the mark, resize its handles, retype the label | | The device angle hides the UI | Accept the one allowed steep angle | Turn the pose a full 360°, tilt to 85°, pick a b-roll move | | A redaction box in the wrong place | Redraw from scratch | Drag, resize, reorder, or nudge it with the arrow keys | | Checking redaction coverage | Commit and hope | Preview result paints the exact fill first | ## Who benefits most **Anyone who documents a moving product.** The button moved, the copy changed, one step is now wrong — and you fix that one step in the preview instead of re-recording a ten-minute flow. **People who care how the demo looks.** The walk-around device, the finish sliders, and the new b-roll moves turn a flat screen capture into something you'd put on a landing page, without exporting to a separate motion tool. **Teams handling anything sensitive.** Editable redaction boxes plus a Preview-result pass mean you can get the coverage exactly right before the fill is permanent — no redraw-and-pray. ## The rest of v1.3.0 There's more in this release than editing. A full **Sound** panel adds Clean voice, Improve microphone audio, duck-under-speech, and a click sound under each cursor press — all mix-time only, so the recorded file is never rewritten. **Captions and chapter cards** bring a nameplate lower-third, two-second chapter cards at each step, and SRT/VTT import and export. And an **Assist** panel offers suggestions you accept or ignore — dead air to cut, harsh cuts that want a b-roll interlude, a grade read from the frame under the playhead, and a highlight reel of the busiest moments. Every one of them is a suggestion, never an automatic edit. ## Try it Open a guide you generated a week ago, press **Edit steps**, and fix the line that always bothered you — then turn the device a few degrees and watch it stop looking like a screenshot. In v1.3.0 the demo you already made is a draft you can keep improving, not a take you have to shoot again. --- ## A Screenshot of a Secret Is Still a Secret Source: https://1showcasetool.com/blog/a-screenshot-of-a-secret-is-still-a-secret Published: 2026-08-13 Tags: redaction, screenshots, security, documentation, privacy Blur, overlays and a later tidy-up do not redact a screenshot. The pixels were written when the frame was captured. Destroy them before they reach disk, or do not claim they are gone. A documentation screenshot is a copy of whatever was on the glass. If a token, an email, or a customer name was in that frame, it is in the file. Compressing the image, dropping it into a slide, or covering it with a grey box in the page CSS does not change that. The pixels are still there. Teams keep learning this the hard way: a setup guide goes out, someone zooms the PNG, and a live key is readable in the noise. The author did not mean to publish a secret. The format did it for them. ## Blur is a visual effect, not a destruction primitive Blur looks like redaction. It is not. Short strings have been recovered from heavy blur for years, and a reader with a contrast slider does not even need a research paper. An outline, a frosted overlay, or a shape sitting on top of the screenshot in the page is worse — any of those can be removed without touching the stored image. The only honest redaction of a screenshot is an opaque fill written into the stored pixels, with no undo. If you painted the wrong region, you recapture. That sounds harsh until you compare it to the alternative: a guide that still contains the thing you thought you hid. ## The leak happens before the export Most documentation tools treat redaction as a last step. Capture first, tidy later. By then the secret has already been encoded, written to disk, and often uploaded so the editor can run in a browser. A later paint job on a cloud copy is theatre. The original frame is already on someone else's machine. If the flow is a web console, the capture itself can refuse to store password fields, one-time codes, and strings that look like keys. That work has to run in the page, before the bitmap is encoded. If the flow is a native window, there is no DOM to inspect, so the tool cannot claim it scrubbed anything automatically. The honest sentence in that case is "nothing was inspected" — not a green badge that says zero warnings. ## A review you can skip is not a review A checkbox labelled "I checked this" next to a Generate button is not a gate. People click it. The only review that changes behaviour is one that *blocks* generate, export, and publish until a human has looked at every kept frame. That pass is also where you name a value and replace every occurrence of it. The guide then carries a placeholder, not the string. A file format that can hold a harvested secret is the wrong format; the schema should reject the document rather than strip the field quietly and pretend it never happened. A browser-only helper that [redacts a screenshot in the tab](https://1showcasetool.com/tools/screenshot-redactor) is useful for a one-off PNG. It is not a substitute for a capture pipeline that never wrote the secret down. ## Desktop captures have no page to inspect Documenting an installer, a preferences pane, or a terminal means capturing pixels with no field names attached. Automatic redaction cannot run. The correct response is a stricter review, not a looser one: you do not acknowledge the pass until you have opened every step you intend to keep. That is also why a display-wide recording and a single-window recording are not the same promise. A display includes notifications, a password-manager thumbnail, the next Slack message. The scoping decision belongs on the record screen, in writing, before the countdown — not in a tooltip after the file exists. ## The file can leak even after the pixels look clean Redaction of the picture is one channel. The container is another. A PNG or JPEG pulled off a phone, a Slack export, or a design tool often still carries EXIF, a software stamp, or a thumbnail of the uncropped frame. If you only paint the pixels you can see, you have not inspected the file. That is a separate job from capture-time redaction. A local metadata viewer is enough for a one-off; a capture pipeline should write a clean bitmap in the first place so there is no thumbnail of the original to recover. Do not upload the suspect file to a "privacy" website to check whether it is private. ## What the file is allowed to contain A useful guide is a list of steps, measured boxes, and pictures of the UI *after* the secrets are gone. It is not a recording of the author's account. Markdown you can commit, a single HTML file that works offline, or an MP4 with the fills already burned in — those are renderers of the same redacted artifact. If a screenshot still contains a secret, the rest of the pipeline is decoration. Destroy the pixels first. Then write the words. The capture loop that makes that possible is the same one in [Record a setup once](https://1showcasetool.com/blog/record-once-followable-guides) — review is a gate, not a setting. ![Review gate with generation and export locked](https://assets.stoicsoft.com/posts/1showcasetool/a-screenshot-of-a-secret-is-still-a-secret/featured.jpg) *Nothing generates, exports, or publishes until every kept frame has been looked through.* --- ## Your screen recording is already the demo — v1.2.0 makes it the film Source: https://1showcasetool.com/blog/screen-recording-to-product-film Published: 2026-08-13 Tags: release, v1.2.0, video, screen recording, editing v1.2.0 sits your recording in a device on a stage, moves a camera through it for a reason, and scores it on your own machine — without re-cutting a single frame of the take. You record the demo in one take. It is correct, it is complete, and it looks like a rectangle of your screen — because that is exactly what it is. So you do the second pass. Export the take, open a motion tool or a mockup site, drop the video into a laptop frame, keyframe a push-in on the part that matters, find a music loop you are allowed to use, hand-fade it under your own voice, and render. Two hours later you have thirty seconds of something worth posting. Then the feature changes, and every one of those two hours has to happen again. The part that stings is that the second pass never adds information. The demo was already right after the first take. Everything after that is presentation — and presentation is a thing software can do. ## What changed v1.2.0 turns a screen recording into a directed film without leaving the app. You sit the take in a device on a stage, pick how aggressively a camera should cover it, mark the moments that deserve a move, and let a locally generated score follow the cuts. The recording underneath is never re-cut: the same frames ship, and the review gate you already acknowledged stays shut. ## How it works in practice ### Put the take somewhere ![Screen recording posed on a living-room television](https://assets.stoicsoft.com/posts/1showcasetool/screen-recording-to-product-film/featured.jpg) *The take sits in a device on a stage. The frames underneath are the same ones you recorded.* A recording no longer has to be a flat rectangle. Pose it in a MacBook Pro, a MacBook Air, a Studio Display, a phone, a tablet, a browser chrome or a plain app window — or hand the camera a shortlist and let it change device at each cut. If the flat take was the right answer, it is still there and looks the way it always did. For the shots that need to land somewhere other than a desk, the same take drops into a real place: roadside billboards, a subway platform, living-room televisions, theater screens, stadium boards, museum galleries, and an unbranded watch face. Each stage carries its own calibrated screen, so the recording sits in the frame rather than floating over it. ### Let a style do the shooting Three film styles decide the coverage on their own. **Launch film** works wide, medium and close from both sides — the default, and the one that reads as a product video. **Feature demo** stays nearly locked off, because a tutorial that swings around is a tutorial nobody finishes. **Social teaser** cuts faster, pushes harder and frames tighter for a feed. An intensity slider decides how far the chosen style goes, and Reshuffle deals the same film again with different coverage when the first pass does not land. The camera is bounded by legibility, not by taste: if a move would smear the interface past readable, the amplitude comes down and the director panel tells you by how much. ### Mark the moments that matter Press `S` at the playhead to say *something happens here*. The director picks an angle for that beat — one that still keeps the screen readable — and pressing `S` again cycles to the next candidate. Pins drag along the ruler, and a pin whose moment a trim removed stays behind as a ghost rather than silently relocating itself somewhere it does not belong. Every pin that did not become a shot prints why: merged into its neighbour, softened, or simply not used. A marker that quietly does nothing is worse than no marker at all. ### Cover the cuts Each gap between clips can pick its own b-roll language, including None. An establishing shot opens the segment wide. An action close-up pushes in as the work starts. A light sweep passes over the device as the segment arrives. There are second-camera angles too — over the shoulder, typing, above the deck, a screen dolly — that play over the head of the next clip. Nothing is inserted into the take: runtime, audio sync and the review gate are all untouched. Only the way a cut is covered changes. ### Give it a score Press **Score this take** and a music bed is generated on this machine, keyed to the film's own cuts rather than looped underneath and hoped for. Calm, Warm, Focus and Bright ship to everyone; Epic and Night unlock with Pro. Duck-under-speech drops the bed while a voice is present, measured here rather than guessed at. The score lives on its own lane. You can split a piece under the playhead, or start a new one — a music cut never re-cuts the picture. If you would rather describe the shape than dial it in, Compose with AI asks the CLI you already connected, on your click and never automatically, and what it receives is the shape of the film — the cuts and the mood — not the footage. ### Say it out loud, and in writing Record a camera track with the screen take and place it on the exported frame: rounded or circle, any corner, or full-frame. It is off until you turn it on. Captions are word-level and produced on this machine — macOS uses on-device speech recognition, while Windows and Linux import an SRT or VTT or take the words you type. Pick Clean, Bold or Karaoke, put them top or bottom, and fix a mis-heard word without touching the audio underneath it. The same captions export as SRT or VTT for wherever else the take is going. ## Before vs After | Getting a shareable demo out | Before v1.2.0 | Now | | --- | --- | --- | | Framing the recording | Export, then rebuild it in a mockup tool | Pick a device and a stage in the studio | | Camera movement | Keyframe every push-in by hand | Pick a style; mark beats with `S` | | Covering a cut | Hard jump, or build a transition | Choose a b-roll language per gap | | Music | Find a loop, clear the licence, hand-fade it | Score this take, pick a mood | | Captions | Upload the audio, wait, burn in the SRT | Transcribed on this machine, styled in the editor | | Changing your mind | Re-render the whole timeline | Reshuffle, or change the style | ## Who benefits most **Founders shipping their own launch video.** The demo you already recorded for the changelog becomes the demo you post, without the two-hour presentation tax or a motion designer's calendar. **Support and documentation teams.** Feature demo mode exists precisely because a training video should not swing around — and the same recording still exports as a written guide, a SCORM 1.2 package your LMS can track, or a PowerPoint deck with one slide per step. **Anyone recording something confidential.** The whole directed layer is cosmetic by construction. Changing style, intensity, markers, b-roll, wallpaper, score, captions or pointer skin leaves the review gate shut, because none of it changes which pixels ship. Trims, masks, clip rates and speed ramps do — so those ask you to watch it back before it goes anywhere. ## The rest of v1.2.0 The studio grew a real timeline, with lanes for clips, click zooms, clicks, masks, shortcut labels, markers and the score. You can split a clip, reorder the pieces, set one clip's playback rate anywhere from a quarter speed to 4x, and put that single clip on a different mockup or background from the rest of the take. The export dialog now asks for resolution, frame rate and quality — with an estimated file size — right before the file is written. The library grew projects, folders and tags over the same set of recordings and guides, plus a grid of first frames so eight takes all called "Entire screen" are still distinguishable. Guide steps got a full annotation editor: crop, arrows, text, shapes, counters, pencil, highlighter, spotlight, image overlays and secure pixelate, with an expiring local-network link when a teammate needs to see it now. And a crash mid-recording no longer poisons every recording after it. The next launch ends any leftover capture process, rebuilds the take from the movies on disk, and says plainly what came back and what did not. ## Try it [Download v1.2.0](https://1showcasetool.com/download) for macOS, Windows or Linux. Record something you would normally have to explain twice, sit it in a device, press `S` where it matters, and let it get scored — then decide whether the second pass was ever really about information. --- ## Record a setup once — get a guide someone can actually follow Source: https://1showcasetool.com/blog/record-once-followable-guides Published: 2026-08-10 Tags: release, v1.1.0, recording, redaction, guides 1ShowcaseTool v1.1.0 turns the click-through you already did into a redacted, AI-written guide with a live overlay — without uploading your session. You have already done the hard part. You clicked through the console, created the key, pasted it into the right field, and somehow the integration just worked. What you do not have is a document someone else can follow without pinging you. Most setup docs fail for the same reason: they are written after the fact, from memory, while the real flow still lives only in the person who just performed it. Screenshots lag. Secrets leak into screenshots. The reader lands on the wrong page and has no idea how to recover. You end up pair-debugging a guide that was supposed to free your time. ## What changed 1ShowcaseTool turns the performance you already did into a guide someone can actually follow. You record the flow once, destroy anything sensitive before it can leave your machine, generate prose with your own AI transport, and either export a static document or hand the guide over so a live overlay points at the next click. This is the first public release — v1.1.0 — with builds for macOS, Windows, and Linux. ## How it works in practice ### Record the flow you already know Open **Record** and pick the capture source that matches the work: - **Record in the browser** for a web console. The Chrome MV3 extension captures each click inside the page, with an ordered selector list and a cropped screenshot per step. Ten developer portals ship pre-approved; every other host is a per-site grant in Chrome's own dialog — the extension never asks for a wildcard. - **Manual screen recorder** or **Auto screen recorder** when the flow leaves the browser. Manual is hotkey-after-each-action on one window; Auto turns every click inside that window into a step without reading your keyboard. - **Screen recording** when you need continuous footage of a display, window, or dragged region — the studio path for takes you will trim and export as video. Browser and desktop capture are mutually exclusive on purpose, so one session cannot silently mix two trust models. ### Review and redact before anything can leave ![Review gate locking generate and export](https://assets.stoicsoft.com/posts/1showcasetool/record-once-followable-guides/review.jpg) *Generation, export and publish stay locked until every kept frame has been looked through.* Every recording lands in **Review and redact**. Nothing generates, exports, or publishes until you acknowledge that pass. Layer 1 already destroyed credential-shaped fields inside the page *before* capture for browser sessions. Layer 2 lets you paint opaque rectangles over stored pixels — not blur, not a reversible overlay. Edits clear the acknowledgement so you cannot ship a stale review by accident. You can also mask values into named placeholders. Later, the follow-along overlay can fill those placeholders for the person walking the guide — without baking the secret into the guide file. The schema rejects a guide that tries to smuggle a secret rather than stripping it quietly. ### Describe the flow, then generate with *your* AI On **Describe the flow**, you tell the model who the guide is for and what matters. That context is most of what separates a usable guide from a list of clicks. Generation runs only when you ask: through an installed agent CLI (Claude Code, Codex, Gemini, OpenCode, Cursor, Aider, and others) or a BYOK API key stored in the OS keychain. Annotation placement comes from the element boxes measured during recording, not from the model guessing coordinates. ### Follow live — or export and ship ![Generated guide with numbered steps](https://assets.stoicsoft.com/posts/1showcasetool/record-once-followable-guides/guide.jpg) *A generated guide is a document — numbered steps, measured marks, no live secrets.* Open **Guide** to preview what a follower sees. For browser-recorded flows, the overlay points at the next target, nudges a wrong click, and offers take-me-back when the page is wrong. When a step produces a value — an API key, a client ID — **value harvesting** can deliver it into the field it belongs to over localhost, with explicit confirmation every time. Prefer a document? Export Markdown, a self-contained HTML file, an animated walkthrough, or MP4 via WebCodecs with no external binary. Studio masks are burned into exported frames so the file you hand over never contained those pixels. ## Before vs After | Before | After | |--------|--------| | You rewrite the same setup in Slack every time a teammate onboarded | You record once and hand them a guide | | Screenshots still show tokens and emails you meant to hide | Secrets are destroyed at capture or painted out with opaque fills | | Docs go stale the moment the console UI moves | Live overlay corrects wrong clicks and wrong pages | | The person who ran the flow is the only person who can help | Value harvesting drops the produced key into the next field on confirmation | | Export needs FFmpeg, a design tool, or a second app | Markdown, HTML, walkthrough, and MP4 leave the same machine | ## Who benefits most **Founders shipping integrations.** You already click through OAuth and webhook setup for every customer-facing recipe. Recording that path once turns support into a guide instead of a calendar invite. **Security-minded teams.** You cannot ship a guide until review is acknowledged, redaction is destructive, and the guide file cannot carry a secret by construction. **Docs writers who inherit half-finished runbooks.** You stop reconstructing steps from memory and start from a trace that already has selectors and screenshots. ## Try it v1.1.0 is the first public build: macOS (Apple Silicon and Intel), Windows x64, and Linux (.deb / AppImage). Free tier blocks nothing on recorders, redaction, or exporters — the first ten guides export clean. Grab the installers from the [v1.1.0 GitHub release](https://github.com/stoicsoft/1showcasetool-releases/releases/tag/v1.1.0) while the download page is wired to the same assets.