3 items
Blur your saved LeetCode solution so you can redo the problem spoiler-free. Peek or reset to a clean slate in one click. Want to hide your previous LeetCode solution so you can redo a problem you've already solved? When you reopen a solved problem, LeetCode auto-restores your old submitted code, which spoils the whole point of practicing again. LeetBlur fixes that. It blurs your previously saved solution behind a frosted overlay the moment the problem loads, and adds two small buttons to the code pane: - Look: reveal your old solution when you're ready to check it. It stays revealed until you open a different problem. - Clear: wipe your old code and reset the editor to LeetCode's starter stub for the current language, so you can redo the problem from a clean slate. The blur only appears when there's an actual solution to hide. A brand-new, template-only editor is left alone, so a fresh problem is never touched. Prefer not to see difficulty labels? Turn on Hide difficulty and LeetBlur hides the Easy, Medium, and Hard tags across LeetCode, on both the problem list and the problem page, so an intimidating "Hard" doesn't psych you out before you start. It's off by default; flip it on any time from the toolbar. You're always in control. Flip blurring or hide-difficulty on or off from the toolbar popup, or from the on-page control button that sits quietly in the corner of every LeetCode page, so your settings are one click away without ever leaving the problem. Your choices are remembered across pages and sessions. Private by design: everything runs locally in your browser. No account, no tracking, no analytics, and no data ever sent to us (we have no servers). The only network request goes to LeetCode's own public API, without your cookies, to fetch the problem's starter template. If you've been looking for a way to hide or cover your previous LeetCode answers so you can practice already-solved problems from scratch, that's exactly what LeetBlur does. Works on https://leetcode.com (blur on problem pages; hide difficulty across the site).
Jul 12, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.