Console Log Cleaner

Clean your production code by removing all console.log statements

JavaScript Tool

Cleaning Level

Cleaned Code

Strip debugging output out of your JavaScript

Debug statements are useful while you build, but leftover console calls clutter the browser console, can leak internal details and add noise for other developers. This cleaner scans the code you paste and deletes the console statements it finds, then tells you how many it removed. It is meant as a quick pre-release pass for scripts, snippets and small files.

How to run it

Paste your script into the JS Source Code box, or press Load Sample to try a small example. Clear empties the box.
Choose a Cleaning Level from the dropdown. Full Sweep removes every listed console method, Only console.log() and Only console.debug() target a single method, and Only profiling removes console.time and console.timeEnd calls.
Click Remove All Logs.
The Cleaned Code panel shows the result with a count such as 3 Statements Removed. Use Copy to take the code.

What the Full Sweep covers

The full option matches log, debug, info, warn, error, table, dir, trace, time, timeEnd, group and groupEnd. That includes console.error and console.warn, so if your code uses those for real error reporting, choose one of the narrower levels instead.

When it is useful

Tidying a script before pasting it into a CMS, a tag manager or a client project.
Cleaning up a code sample before publishing it in a tutorial.
Removing timing calls after you finish a quick performance check.
Reviewing how many stray logs an inherited file contains.

Read this before trusting the output

The tool uses a pattern match on single lines, not a real JavaScript parser. Each match runs from console. to the end of the line, so anything after the call on the same line is removed with it, such as a second statement or a trailing comment. A console call that is spread over several lines is only partly removed and can leave broken syntax. Console text inside strings or comments is also matched, and removing a call that is the only body of an if statement without braces changes the logic of your code. Empty lines and indentation are left behind. Always read the cleaned code, run your tests, and keep the original. For serious production builds, a bundler option such as dropping console in your minifier is more reliable. The processing runs in your browser.

Related Tools

Frequently Asked Questions

Which console methods does Full Sweep remove?

log, debug, info, warn, error, table, dir, trace, time, timeEnd, group and groupEnd. Because that list includes warn and error, use a narrower level if you want to keep real error reporting in the code.

Can it break my code?

Yes, in some cases. It matches text line by line rather than parsing JavaScript, so multi-line console calls, statements sharing a line with a log, and unbraced if bodies can end up broken. Review the output and test it before using it.

Does it remove multi-line console.log calls?

Not reliably. The match stops at the end of the line, so a call written across several lines is only partly removed and may leave unbalanced brackets. Put such calls on one line first, or delete them by hand.

Why was extra code on the same line deleted?

The pattern removes everything from console. to the end of that line, including any statement or comment that follows. Put each statement on its own line before cleaning if you want to avoid losing other code.

What does the Statements Removed number mean?

It is the number of pattern matches found for the chosen cleaning level, meaning how many lines had a matching console call. Multi-line calls count once, even though they may not be removed entirely.