LOGIN Try Free

Made for performance-first creators.

Less is enough.

Set the Minimum Log Level

LessFlux logs events during image and video processing. The minimum log level setting controls how much information is recorded in those logs.

This setting is mainly used for troubleshooting. It does not affect how optimization works, only how much visibility you have into what is happening.

Where to find this setting

  • Go to LessFlux settings
  • Find the “Minimum Log Level” option under General Options
  • Select the desired level from the dropdown

Available log levels

Error – Only errors

Logs only critical issues that prevent processing from completing.

  • minimal logging
  • only shows failures
  • best for normal usage

Warning – Warnings and errors

Logs errors and potential issues that do not always stop processing.

  • shows skipped files, partial processing, and warnings
  • useful for identifying misconfigurations
  • recommended during setup or troubleshooting

Info – All information

Logs most actions performed by the system.

  • includes successful operations
  • provides full visibility into processing flow
  • can generate a large number of log entries

Debug – Detailed debug info

Logs everything, including detailed internal operations.

  • used for deep troubleshooting
  • can be noisy and harder to read
  • should only be enabled temporarily

For most websites, use:

  • Error – Only errors (normal operation)

If you are setting up LessFlux for the first time or diagnosing an issue, use:

  • Warning – Warnings and errors

This gives enough visibility without overwhelming the logs.

When to change the log level

  • use Warning when something is not behaving as expected
  • use Info if you need to trace what the system is doing
  • use Debug only when investigating complex issues

After troubleshooting, always switch back to a lower level.

How to use logs effectively

  • check logs when files show Failed, Ignored, or Could not process
  • look for patterns, not just single errors
  • combine log messages with file statuses for context

Logs are not meant to be monitored constantly. They are a tool to understand problems when something goes wrong.

Common mistakes

  • leaving Debug enabled in production
  • ignoring warnings that indicate configuration issues
  • expecting logs to show every processed file at lower levels

If everything is working correctly, logs should stay minimal most of the time.

Best practices

  • use Error level for normal operation
  • switch to Warning when diagnosing issues
  • avoid using Info or Debug unless necessary
  • reduce log level after troubleshooting

The goal of logging is clarity when you need it, not constant visibility.