Make filter definitions user‑editable (move extension lists from the executable to a JSON file)

[LocalAdmin]

Hello David,

Currently, the built‑in filters (Documents, Images, Videos, Audio, Executables, Compressed, etc.) have their file extension lists hardcoded inside the executable. This makes it impossible for users to add modern formats such as:
.md
.json
.yaml / .yml
.toml
.ini
and many others.

It would be extremely useful if the filter definitions could be externalized into a file such as "filters.json", allowing users to edit or extend the extension lists without modifying the executable.

Benefits:

Users can customize filters to match modern workflows
No need to hex‑edit the executable
Filters become update‑safe
Developers can share custom filter sets
Everything becomes more flexible for power users

This would be a small change with a huge impact.

Thank you for considering this improvement.

[therube]

It's there already.

Search | Organize Filters

And if changes are made, then they're stored in a Filters.csv file.