Item logo image for EzzyTyper

EzzyTyper

5.0(

3 ratings

)
ExtensionDeveloper Tools13 users
Item media 3 (screenshot) for EzzyTyper
Item media 1 (screenshot) for EzzyTyper
Item media 2 (screenshot) for EzzyTyper
Item media 3 (screenshot) for EzzyTyper
Item media 1 (screenshot) for EzzyTyper
Item media 1 (screenshot) for EzzyTyper
Item media 2 (screenshot) for EzzyTyper
Item media 3 (screenshot) for EzzyTyper

Overview

Simulate human typing in Google Docs at 10–50 WPM with realistic breaks and mistakes.

EzzyTyper — Dev-Ready Docs (copy/paste) This is a single, ready-to-paste document you can drop into your repo as README.md, share with your team, or repurpose for the Chrome Web Store listing. It includes overview, features, FAQs, troubleshooting, privacy, and listing copy. What is EzzyTyper? EzzyTyper is a lightweight typing engine that simulates human typing inside editors like Google Docs. It types at a realistic 10–50 WPM, inserts small, deliberate mistakes based on your Accuracy slider, takes micro/long breaks, and shows a live status bar (micro-break countdown, long-break ETA/left, % complete, last mistake preview, and overall ETA). Use it for demos, dictation cleanup, content “replay,” or simulating realistic human input in tests. Features Human pace: 10–50 WPM with timing jitter and optional half-word hesitations. Word-level accuracy: Pick an accuracy (e.g., 90%). Exactly (100 – accuracy)% of words get one wrong character (kept in the output). Random backspaces (0–30%): occasional “stumbles” that delete and retype the same characters (no autocorrection). Breaks: Micro-breaks: probability-based frequency (0–30%), duration range (0–180s). Long breaks: occur every N minutes, with a random duration between your min/max minutes. Dual UI modes: Expanded (compact controls). Minimized (bigger buttons & title, persistent status line). Live status chips: Micro-break (countdown or N/A), Long-break (mm:ss left or N/A / next-in), % complete, ETA, and Last mistake (with the substituted character highlighted). Google Docs–aware: Works inside Docs’ editor iframe; includes a focus helper. Keyboard toggle: Ctrl + Shift + E to show/hide the panel. Controls in both views: Start/Stop and Pause/Resume. How it Works (Quick) Click into your target editor (e.g., Google Docs). Open EzzyTyper, paste or type the text to “type out.” Adjust sliders (WPM, Accuracy, micro/long break settings, etc.). Press Start Typing. The status chips update in real time (micro-break seconds left, long-break left/in, last mistake, % complete, ETA). Sliders & Toggles Explained WPM (10–50): Overall pace. Internally paced at ~5 chars per word. Accuracy (0–100%): Per word. If Accuracy = 90, ~10% of words will have one wrong character (kept as a mistake). Correction speed (s): Delay used when a random backspace “stumble” happens (retyping the same chars). Micro-break frequency (0–30%): Approx probability per character to schedule a micro-break. The engine spaces them to avoid spammy pauses. Micro-break duration range (s): Random duration between min & max (0–180s). Half-word pauses (toggle): Extra micro hesitations mid-word (human flavor). Random backspace (toggle) + chance (0–30%): Occasional delete + retype of recent chars (not a correction). Long-break duration (min): Random duration between min & max. Long break every (min): Fixed cadence. At the interval, a long break starts with a random duration in your min/max. Text: The content EzzyTyper will type. Permissions & Why activeTab / scripting — Injects the small typing “bridge” into the current page so keystrokes register in iframes (e.g., Google Docs). clipboardWrite (optional / fallback) — Enables a rare “paste chunk” fallback when an editor blocks synthetic key events. Host permissions (optional) — https://docs.google.com/* can improve reliability for Google Docs. Privacy-first: No analytics. No network calls. No data leaves your browser. The extension only simulates events in the focused editor tab. FAQ Q: It won’t type — what do I do? A: Click once inside the editor to focus it, then press Start. Google Docs requires focus inside its iframe. The extension also tries to focus automatically, but some pages block programmatic focus. Q: Accuracy 90% doesn’t “look” right. A: Accuracy is enforced per word: (100–accuracy)% of words get exactly one character substituted. Over short passages, random variation can look noisy; over long passages it matches closely. Q: Why do I see mistakes in status but not in the doc? A: Ensure your editor isn’t auto-correcting (e.g., spell-check that replaces characters). EzzyTyper keeps mistakes; it doesn’t fix them. Q: What does “Micro-break N/A” mean? A: No micro-break active right now. When a micro-break starts, the chip shows a live countdown. Q: What about long breaks? A: Status shows “mm:ss left” when active, or “in Xm” until the next one (or N/A if not scheduled yet). Q: Backspaces don’t fix typos? A: Correct — backspace events are stumbles. The same removed chars are retyped. To preserve the “human” vibe, mistakes stay. Q: Will it work outside Google Docs? A: Yes, for most contenteditable, textarea, and many input fields. Some web apps block synthetic events; the clipboard fallback helps, but not always. Q: How do I stop it quickly? A: Hit Stop (or Pause, then Stop). You can also hide the panel with Ctrl + Shift + E. Troubleshooting No text appears Click inside the editor and try Start again. Disable site extensions that hijack input. In Docs, ensure Editing mode (not Suggesting/Viewing). Too many breaks Lower Micro-break frequency and increase Long break every. ETA jumps Normal — ETA is based on remaining characters and dynamic WPM (with jitter). Spaces missing Some editors auto-collapse or normalize whitespace on synthetic events. Consider enabling the clipboard fallback in code paths if needed. Nothing happens after Start Reload the tab (content script reinjection can be required on some pages). Known Limitations Some editors ignore synthetic KeyboardEvents (security/anti-automation). Browser spell-check/autocorrect can hide or “fix” deliberate mistakes. Canvas or highly custom editors may not register synthetic typing. Shortcuts Toggle panel: Ctrl + Shift + E Chrome Web Store Listing Copy Short description (≤ ~80 chars) Simulate human typing in Docs & editors: 10–50 WPM, realistic mistakes & breaks. Long description EzzyTyper types your text into editors (like Google Docs) at a human pace (10–50 WPM), with optional micro & long breaks, realistic hesitations, and word-level accuracy (one wrong char in the chosen share of words). It shows a live status line (micro-break countdown, long-break ETA/left, % complete, ETA, and last mistake preview). Word-level accuracy with kept mistakes Micro-breaks (0–30% frequency, 0–180s range) Long breaks (every N minutes, random duration min–max) Random backspace stumbles (0–30%), no auto-correction Dual UI (expanded/minimized) + keyboard toggle Privacy-first: no analytics, no data leaves your browser. Privacy (Template) EzzyTyper does not collect, store, or transmit personal data. No analytics. No remote servers. Actions take place locally in your browser tab. If you open a GitHub issue, please don’t include sensitive text or documents. Changelog (Template) 1.0.0 — Initial release: 10–50 WPM, word-level accuracy, micro/long breaks, minimized UI, live status chips.

Details

  • Version
    1.7.3
  • Updated
    August 23, 2025
  • Offered by
    muhammadezzein
  • Size
    177KiB
  • Languages
    English
  • Developer
    muhammad ezzein
    9754 Mustang trail Fishers, IN 46040 US
    Email
    muhammadezzein@gmail.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

The developer has disclosed that it will not collect or use your data. To learn more, see the developer’s privacy policy.

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, please open this page on your desktop browser

Google apps