Skip to content

fix: better explain file size limit #215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
secDre4mer merged 1 commit into from
Oct 13, 2026
Merged

fix: better explain file size limit #215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions scanning/using-thor.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -259,11 +259,9 @@ File Size Limit
---------------

The default file size limit for content checks such as hash calculation
and YARA scanning is ``64 MB``. In ``--deep`` scan mode, the limit is
``200 MB``.

You can adjust the values in ``./config/thor.yml``. This file does not
get overwritten by an update or upgrade.
and YARA scanning is ``64 MB``. In ``--deep`` scan mode, the default limit
is raised to ``200 MB``. In either mode, you can override the default
with ``--file-size-limit``.

Some features, such as EVTX or memory dump scanning, ignore these
limits. See :ref:`scanning/features:Features` for a full list of features
Expand Down
Loading