# Log Cleanup

The log cleanup feature is used to scan and clean up log files generated by the system and applications to free up disk space.

![Log Cleanup](/images/toolbox/toolbox-log.png)

## Feature Overview

The top of the page provides batch operation buttons:

- **Scan All**: Scan all types of logs
- **Clean All**: Clean all scanned logs

## Log Types

### Panel Logs

Log files generated by panel operation.

- Click **Scan** to check log size
- Click **Clean** to delete log files

### Website Logs

Website access logs and error logs, including:

- Nginx access logs (access.log)
- Nginx error logs (error.log)
- Individual logs for each website

::: tip Tip
Website logs are usually the largest type of logs, it is recommended to clean them regularly.
:::

### MySQL Logs

Log files for Percona/MySQL/MariaDB databases:

- Slow query log
- Binary log (binlog)
- Error log

::: warning Note
Binary logs are used for data recovery and master-slave replication, please confirm they are no longer needed before cleaning.
:::

### Docker

Docker-related logs and unused resources:

- Container logs
- Unused images
- Build cache

### System Logs

System-level log files:

- systemd journal logs
- System logs under `/var/log`
- Kernel logs

## Usage

1. Click the **Scan** button for each type to view log space usage
2. Confirm the log types to clean
3. Click the **Clean** button to delete logs

Or:

1. Click **Scan All** to scan all logs at once
2. View the usage of each type
3. Click **Clean All** to batch clean

## Notes

1. Cleanup operations are irreversible, please confirm logs are no longer needed
2. Important logs should be backed up first
3. In production environments, it is recommended to keep recent logs for troubleshooting