# Runtime Options

These are higher level options that effect the overarching functions of the program.

## `console_log_level`

| Type             | Default |
| ---------------- | ------- |
| `NonNegativeInt` | `100`   |

Same as `log_level` but it controls which messages are shown on the console.

{% hint style="info" %}
This option is ignored unless CDL is running with `--ui DISABLED`
{% endhint %}

## `deep_scrape`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

Cyberdrop-DL uses a some tricks to try to reduce the number of requests it needs to make while scraping a site. However, this may cause a few links to be skipped. Use `--deep-scrape` to disable this functionality and always make a new request.

This setting is temporary and will always reset to `false` after each run

{% hint style="warning" %}
Use this option only when absolutely necessary, as it will significantly increase the number of requests being made.

For example, scraping an album normally takes one single request.

With `--deep-scrape`, CDL will make `n` requests per album, where `n` is the total number of items in the album
{% endhint %}

## `delete_partial_files`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

Files downloaded by CDL have a `.part` extension (`.cdl_hls` for HLS segments). CDL only changes the extension to the original one after a successful download. This allows CDL to resume downloads on subsequent runs.

Setting this to `true` will delete any `.part` and `.cdl_hls` files in the download folder.

## `ignore_history`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

By default, the program tracks your downloads in a database to prevent downloading the same files multiple times, to save time and reduce strain on the servers you're downloading from.

Setting this to `true` will cause the program to ignore the database, and will allow you to re-download files.

## `jdownloader_autostart`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

Setting this to `true` will make jdownloader start downloads as soon as they are sent.

{% hint style="info" %}
This option has no effect unless `send_unsupported_to_jdownloader` is `true`
{% endhint %}

## `jdownloader_download_dir`

| Type             | Default |
| ---------------- | ------- |
| `Path` or `null` | `null`  |

The `download_dir` jdownloader will use. A `null` value (the default) will make jdownloader use the same `download_dir` as Cyberdrop-DL. Use this option as path mapping when jdownloader is running on a different host / docker.

{% hint style="info" %}
This option has no effect unless `send_unsupported_to_jdownloader` is `true`
{% endhint %}

## `jdownloader_whitelist`

| Type                | Default |
| ------------------- | ------- |
| `list[NonEmptyStr]` | `[]`    |

List of domain names. An unsupported URL will only be sent to jdownloader if its host is found on the list. An empty whitelist (the default) will disable this functionality, sending any unsupported URL to jdownloader.

{% hint style="info" %}
This option has no effect unless `send_unsupported_to_jdownloader` is `true`
{% endhint %}

## `log_level`

| Type             | Default |
| ---------------- | ------- |
| `NonNegativeInt` | `10`    |

Defines the logging level for messages, according to [Python logging levels](https://docs.python.org/3/library/logging.html#levels). Only messages with a level equal or greater than this setting will be logged, with the exception of `NOTSET` which will disable all logging messages. Setting a value above 50 will also disable logging entirely.

| Level      | Value | Description                                                                                        |
| ---------- | ----- | -------------------------------------------------------------------------------------------------- |
| `NOTSET`   | 0     | Disables all log messages                                                                          |
| `DEBUG`    | 10    | Offers detailed information, typically useful to troubleshoot problems                             |
| `INFO`     | 20    | Provides general information about scrape and download progress                                    |
| `WARNING`  | 30    | Potential issues or something that might need attention (e.g. `Login wasn't provided for <FORUM>`) |
| `ERROR`    | 40    | Serious problem preventing Cyberdrop-DL to execute some function                                   |
| `CRITICAL` | 50    | Fatal error that causes Cyberdrop-DL to exit immediately                                           |

{% hint style="info" %}
Using anything other that `DEBUG` makes troubleshooting issues harder. Practically speaking, you should *only* change this if you expect CDL to run for an extended period (with a large number of input URLs) to minimize the log files sizes
{% endhint %}

{% hint style="info" %}
There is one more verbose level of logs: `DEVELOPER`

It includes pager logs, posts logs, individual requests logs (their URLs and their response code), requests cache hits and misses, file system locks logs and local variable values from within a traceback. It's not exposed as a config option because it is too verbose.

You can set the environment variable `CDL_DEBUG_LOG_FOLDER` to any valid folder and CDL will create an additional log file with the level set to `DEVELOPER` inside it.
{% endhint %}

{% hint style="warning" %}
As the name suggests, the `DEVELOPER` log level is only meant for developers or, more generally, people that want and have the know how to troubleshoot CDL issues on their own. You should never share those logs with *anyone* as it could potentially have raw information in the tracebacks like cookies, auth credentials, IPs, etc.
{% endhint %}

## `send_unsupported_to_jdownloader`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

Cyberdrop-DL has integration with jdownloader. This will allow you to download URLs that Cyberdrop-DL finds but do not support. However, this setting is disabled by default.

Setting this to `true`, will send unsupported links over.

## `skip_check_for_empty_folders`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

After a run is complete, the program will do a check (and remove) any empty files and folders in the download and scan folder.

Setting this to `true` will disable this functionality.

## `skip_check_for_partial_files`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

After a run is complete, the program will do a check to see if any partially downloaded files remain in the downloads folder and will notify you of them.

Setting this to `true` will skip this check.

## `slow_download_speed`

| Type       | Default |
| ---------- | ------- |
| `ByteSize` | `0`     |

{% hint style="info" %}
This setting specifies speed and it's interpreted as `<value> / second`. ex: `8MB` means `8MB/s`
{% endhint %}

Downloads with a speed lower than this value for more than 10 seconds will be skipped. Set to `0` to disable

## `update_last_forum_post`

| Type   | Default |
| ------ | ------- |
| `bool` | `false` |

Updates `input_file` content, adding the last scraped post id to every forum thread URL


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://script-ware.gitbook.io/cyberdrop-dl/reference/configuration-options/settings/runtime_options.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.