Fake is a Mac-native browser built specifically for scripting, automating, and testing web workflows without touching a line of command-line tooling.
What is Fake?
Fake is a dedicated automation browser for macOS that lets you record, edit, and replay sequences of web interactions — form submissions, button clicks, navigation flows — through a visual, script-driven interface. Unlike a general-purpose browser, every feature in Fake exists to serve one goal: making web automation accessible without forcing you into a headless terminal session.
I stumbled onto Fake after spending an embarrassing number of hours wrestling with Selenium boilerplate for a repetitive login-and-scrape workflow. Within an afternoon I had the same task running cleanly, with readable steps I could tweak between runs.
What does Fake do best?
Fake excels at turning fiddly, multi-step browser interactions into repeatable, editable scripts — right on your Mac, with no external dependencies to install. The script editor sits alongside a live browser pane, so you see exactly what each action does the moment you run it.
- Action-based scripting: Steps like "click element", "fill field", "wait for selector" are first-class objects you arrange and reorder — closer to a workflow builder than raw code.
- JavaScript injection: Drop into JS at any point in a script when you need logic the visual layer can't express.
- Session recording: Browse normally and Fake records the interaction into a replayable script — a useful starting point you then refine.
- Scheduling & loops: Run scripts on a timer or repeat a sequence over a list of inputs, which is handy for batch testing or data collection.
Where Fake pulls ahead of raw AppleScript-driving-Safari hacks is legibility. A six-step login flow reads like a numbered checklist, not cryptic event descriptors.
Who should use Fake?
Fake is ideal for Mac users who need browser automation but aren't professional QA engineers with a Playwright or Cypress setup already running. Think: indie developers smoke-testing their own web apps, researchers collecting structured data from sites that don't offer APIs, and operations folk automating repetitive internal web portals.
If you're already comfortable with Playwright, Puppeteer, or Selenium in a CI pipeline, Fake won't replace those — they handle parallelism, cross-browser targets, and CI integration far better. But for a solo Mac user who just needs something to run reliably while they grab coffee, Fake is considerably less friction.
It also occupies a niche that tools like Shortcuts and Automator can't fill: those tools are app-automation frameworks, not browser-automation environments. Fake understands the DOM.
Is Fake free?
Fake is available as a free download from the developer's site and through Homebrew Cask. Check fakeapp.com for the current licensing model, as the developer has offered both free and paid tiers at different points in the app's life. Core scripting and replay functionality has historically been available without a purchase.
What are the best Fake alternatives?
The closest native Mac alternative is UI Browser combined with AppleScript, though that approach is verbose and brittle across site updates. For developer-oriented automation, Playwright and Cypress are the industry standards — massively more capable, but they demand a Node.js project and a terminal mindset. Selenium IDE is a browser extension offering record-and-replay in Chrome and Firefox, though it lacks Fake's Mac-native feel and tight script-editor integration. For no-code users, Zapier and Make (formerly Integromat) cover web-to-web automation when APIs exist — Fake handles the cases where they don't.
How does Fake compare to Selenium IDE?
Selenium IDE lives inside your everyday browser as an extension, which means it records against whatever Chrome or Firefox session you already have open — convenient but occasionally messy. Fake runs as a self-contained Mac app with its own browser engine, so your automation environment is isolated from your personal browsing. Fake's script editor also feels more at home on macOS (native menus, keyboard shortcuts, document model), whereas Selenium IDE inherits the constraints of browser-extension UI. The trade-off: Selenium IDE exports to multiple languages and plugs into CI runners directly; Fake is built for solo, on-Mac use.
