Passive Voice Detector — Find & Fix Weak Sentences
Scan text for passive voice constructions and highlight them alongside active sentences.
How it works
- 1Paste or type your text in the input field
- 2Click "Process" — processing happens in your browser
- 3Copy the result or download as a text file
What to do next
About Passive Voice Detector
Passive Voice Detector is a self-contained text processing workspace. Scan text for passive voice constructions and highlight them alongside active sentences. Open the page, get the result, close the tab — that is the entire workflow.
Passive Voice Detector is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.
Passive Voice Detector performs the transformation entirely inside the JavaScript runtime. Your file lives in the tab's memory while the engine works on it; the result lives in the tab's memory until the browser triggers the download. Both are released when the tab closes, the way every browser tab releases its memory.
Architecturally, Passive Voice Detector is a single-page client. The processing layer is standard browser APIs; the UI is a thin React shell on top. Inputs flow through the engine and the output is returned to the browser as a Blob you can save or copy. The 0 MB cap is the only hard limit and it exists to keep memory usage stable on every device.
A practical note on limits: Passive Voice Detector accepts inputs up to 0 MB per run, and the tool processes one input at a time to keep memory usage predictable. If you ever bump into the ceiling, the cause is the size of the input.
Typical users of Passive Voice Detector include researchers normalising scraped text, marketers polishing product copy and translators aligning bilingual passages. The thread connecting all of them is the same: a focused text processing task that fits cleanly into a browser tab and benefits from a tool with sensible defaults and minimal setup.
The download is delivered as a clearly named file the moment processing completes — no email link, no "your result will be ready in 5 minutes" queue, no expiry timer. The file is generated in your browser and saved by your browser's normal download flow.
Passive Voice Detector sits in a small group of related tools. Useful neighbours include Duplicate Sentence Finder, Text to Outline, Readability Score, and Word Counter. They are designed to compose: the output of one is a sensible input to the next, so a multi-step task is usually a sequence of single-click operations.
Some notes on the design of Passive Voice Detector. The page is intentionally narrow: one input, the controls relevant to the task, and one output. Adding unrelated features would make the common case slower for the majority of users, so the surface is held to what people actually use.
Some context on why Passive Voice Detector exists in this form: modern File APIs, high-performance JavaScript engines, and well-maintained open-source libraries now make it possible to perform text processing work entirely in the browser. Passive Voice Detector is built on top of that capability, which is why a single page can host the full pipeline.
If you also use a command-line tool for passive voice detector, Passive Voice Detector is a convenient alternative for the times you are on a different machine or helping someone who is not comfortable in a terminal. The output is a standard file in the format documented above.
A few practical tips that experienced users of Passive Voice Detector pick up over time. First, keep your default browser updated — the engine relies on standard web APIs and newer browser versions are noticeably faster than ones from a few years ago. Second, close other heavy tabs before processing a large input; the engine shares CPU and memory with whatever else is open. Third, if you re-run the same kind of job often, your last-used settings are remembered for the rest of the tab session, so subsequent runs are essentially one click.
If Passive Voice Detector appears to hang, the engine is almost certainly still working — large inputs simply take longer to process inside a browser than they would on a server with multi-core scheduling. For inputs near the 0 MB cap, give it up to a minute on a typical laptop before assuming something is stuck.
Passive Voice Detector is one of many single-purpose tools in the catalog. Each is built around the same single-page model. Use this one, close the tab, and come back the next time you need the same job done. None of the tools require prior knowledge of the others — each page is self-contained.
How it works
- 1Reach the Passive Voice Detector page in your browser to begin.
- 2Drop a text file onto the upload area, or click to pick one from your device.
- 3Pick any non-default settings you need. Most users leave the defaults alone for the first run and only revisit if the result needs tuning.
- 4Trigger processing. standard browser APIs reads your input, applies the transformation, and writes the result back into the page.
- 5Download the result. The file is generated in your browser and saved through your normal download flow.
- 6Repeat the process for additional inputs whenever you need to. The page stays loaded, so subsequent runs are quick.
Common use cases
- Count the words in a draft to check it fits a brief using Passive Voice Detector.
- Re-case a title from ALL CAPS to Title Case.
- Encode user input safely before pasting it into HTML.
- Reformat a JSON blob copied from a log into something readable.
- Strip messy formatting out of copy pasted from a PDF.
- De-duplicate a list of email addresses pulled from a form export.
- Convert a column of names into a comma-separated list for a script.
- Generate a slug from a long article title.
- Translate plain text into Markdown for a static-site post.
- Diff two drafts of a document side by side.
FAQ
How does it detect passive voice?
It scans for "be" verb + past participle patterns (e.g., "was taken", "is broken") that commonly indicate passive constructions.
Is passive voice always bad?
No — passive voice is appropriate for emphasis on the action rather than the actor. This tool helps you find it so you can decide.
Does it catch all passive constructions?
It catches the most common patterns. Some complex or irregular forms may be missed by the heuristic approach.
Can I paste long documents?
Yes — the tool processes text of any reasonable length directly in your browser.
Does it modify my text?
No — it only highlights and categorizes sentences. You make the edits yourself.
Is my data safe?
Yes — all processing happens locally in your browser. Your text never leaves your device.
Do I need to install anything to use Passive Voice Detector?
No installation is needed. Passive Voice Detector runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use Passive Voice Detector on any computer you have temporary access to without leaving anything installed on it.
Will I notice a difference in the output from Passive Voice Detector?
Passive Voice Detector is built to preserve quality wherever the underlying text format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.
Does Favtoo keep a copy of files I process with Passive Voice Detector?
Favtoo keeps no copy of your file because Favtoo never receives your file. Passive Voice Detector runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
Can I use Passive Voice Detector on iOS or Android?
Passive Voice Detector runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 0 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.
Does Passive Voice Detector have an API?
Passive Voice Detector is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (standard browser APIs) is open-source and can be used directly from your own code.
Is the source for Passive Voice Detector available?
Passive Voice Detector is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (standard browser APIs) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
How do I know I am using the latest version of Passive Voice Detector?
Passive Voice Detector is updated whenever the underlying engine releases an improvement or a bug fix. Because the tool is delivered as a static page, every visit fetches the latest version automatically — there is no "version" to manage on your end. If a particular release ever changes default behaviour, the change is documented on Favtoo's changelog so you can confirm what shifted.