Skip to content
Your files stay on your computer

How bruhgrow works.

bruhgrow.com looks like any file-conversion website, but it does not have an upload step. The 100 tools are programs that run inside your browser, on your own device.

What happens when you drop a file

  1. 1

    The tool loads its engine

    The page downloads the code it needs (for example FFmpeg compiled to WebAssembly) and caches it. The next time, it starts instantly.

  2. 2

    Your file stays in the tab

    The browser reads the file into memory. It is never sent to a server; bruhgrow does not have one that accepts files.

  3. 3

    The result is written to your disk

    The tool processes the file on your CPU and hands you a new file to save. Close the tab and nothing remains anywhere.

Under the hood

Mature open-source engines, compiled to WebAssembly so they run in a browser tab.

Audio & video

A WebAssembly build of FFmpeg, the same encoder behind most desktop video apps, runs inside the page. Compressing, converting, trimming, extracting audio and removing silence are FFmpeg jobs executed on your CPU.

Audio & video tools

PDF

pdf.js renders pages, pdf-lib rewrites documents, and qpdf (compiled to WebAssembly) handles encryption, repair and compression. OCR uses Tesseract, also in WebAssembly.

PDF tools

Images

The browser’s own canvas and image codecs do most of the work; WebAssembly decoders and encoders cover HEIC, AVIF and other formats the browser cannot read or write natively.

Image tools

Subtitles

Speech recognition uses a Whisper model that runs on your device. The model is downloaded once, cached by the browser, and never sends audio anywhere.

Where the limits are

Running on your device means the device sets the limits. In practice these are the ones you will meet.

  • Memory. The browser holds the whole file in RAM while working on it. About 1 GB per audio or video file is a practical ceiling on most computers; PDFs and images are rarely a problem.
  • Time. Re-encoding video is CPU-bound. A long 1080p video takes roughly real time on a recent laptop and longer on older or low-power machines. Audio-only and PDF jobs are quick.
  • Battery. Heavy jobs use the CPU fully. On a laptop, plug in for a long encode.
  • Browser. A current Chrome, Edge, Firefox or Safari on a desktop works best. Mobile browsers work for small and medium files.

Web app + Mac app

The license, in three lines.

See pricing
  1. 1

    Try every tool free

    Open any tool, drop a file and see the result. No account is needed to try.

  2. 2

    Save with the lifetime license

    One payment unlocks saving on every tool, forever, including tools added later. There is no subscription.

  3. 3

    Web and Mac, one license

    Sign in on the web with the email you paid with. The native Mac app uses the same license and works fully offline.

Questions

Are my files uploaded anywhere?
No. Every tool runs inside your browser, or fully offline in the Mac app. The site does not have a server that receives files.
How can a web page run FFmpeg?
FFmpeg is compiled to WebAssembly, a format browsers can execute at near-native speed. The code is downloaded like any script and runs on your computer.
Why is the first run of a tool slower?
The tool’s engine (for example the FFmpeg or Whisper files) is downloaded the first time and cached by the browser. Later runs start immediately.
Is there a file size limit?
No hard limit, but the file has to fit in your browser’s memory. Around 1 GB per media file is a sensible maximum; the Mac app handles larger files more comfortably.
What do I get for $9?
Every tool on the web and in the Mac app, forever, plus every tool we add later. It’s the early-bird price for the first 50 supporters; after that the license costs $39.
Can I use it on more than one Mac?
One license is active on one Mac at a time. Got a new Mac? Activate there and the old one signs out.