pickfit

BrowseOther

QuickRecorder

Lightweight screen recorder for macOS based on ScreenCapture Kit.

Tested on macOS

Use it

macOS arm64

  1. brew tap and install QuickRecorder cask to ~/Applications

    brew tap lihaoyun6/tap 2>&1 && brew trust --tap lihaoyun6/tap 2>&1; brew install --cask --appdir=$HOME/Applications lihaoyun6/tap/quickrecorder
  2. remove Gatekeeper quarantine (app not notarized, Apple Development signature)

    xattr -dr com.apple.quarantine ~/Applications/QuickRecorder.app 2>&1 && xattr -l ~/Applications/QuickRecorder.app

First thing to try

open ~/Applications/QuickRecorder.app

What it does

  • Record screens windows and applications
    Not tested
  • Record audio loopback without driver
    Not tested
  • Overlay camera in real time
    Not tested
  • Record HEVC with Alpha video
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Opens
  3. 0 of 4 features work
  4. Works offline

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

It opens to its main screen

  • Replayed from scratch
  • Checked on 4 Nov 2026
  • Version 1.6.7

When pickfit opened it, its main screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: brew install lihaoyun6/tap/quickrecorder
    In the test: needs brew tap lihaoyun6/tap && brew trust --tap lihaoyun6/tap and --appdir=$HOME/Applications because $HOME is /Users/sbx and /Applications is not writable without sudo
  • README: app launches after brew install
    In the test: app is signed with Apple Development certificate (RLYLNV942Y) and not notarized (spctl shows Apple Development origin), so macOS quarantines it and open fails until xattr -dr com.apple.quarantine ~/Applications/QuickRecorder.app

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.