Categories group transfers so you can find and manage them more easily. They can also select a destination for completed files and assign preferences to new entries. They are organisational tools, not separate download networks.

Create one useful category first

Right-click an existing category tab to find the category controls in the standard interface. Add a clearly named category, such as Reference documents, and choose its optional settings. Start with one purpose rather than creating a long list of overlapping labels.

Assign a transfer through its context menu or the supported drag-and-drop action. Check the resulting tab and state before applying an operation to a larger selection. Menu labels may vary between builds, but the project's category documentation explains the underlying controls.

Separate a category from a view filter

The first category can show all downloads or apply a filter for a type or state. A transfer that disappears from a filtered view may still exist in the list. Clear the view filter and select All before concluding that its data has gone.

This is a useful first check when only some entries are missing after changing how the list is displayed. A vanished row is not automatically a damaged metadata file requiring the recovery procedure.

Choose a category-specific completion folder

A category can specify its own Incoming destination. If left empty, the normal default is used. Confirm that an explicit destination exists, is writable and has room for completed files. Check the full path, especially on removable drives.

An Incoming destination is part of the sharing arrangement. Do not point a category at a folder mixing public downloads with private documents. Review the sharing checklist before treating a new storage location as private.

Test automatic assignment with a narrow pattern

The documented assignment syntax supports * as a wildcard and | between alternatives. For example, a rule such as *.pdf|*.txt describes two filename patterns. Use an example that fits material you are entitled to obtain, and check how your build applies it to new downloads.

Broad rules can overlap. Before relying on one, compare the intended category with the outcome of a small controlled test. Do not assume that adding a rule has reorganised every existing transfer or moved files that already completed.

Understand priority and group actions

Category controls can apply actions to several transfers. Read the selection and command carefully: Pause, Stop, Resume and Cancel do not have the same effect. Changing the category's default for new files is also different from explicitly changing every existing entry.

A local priority is not an instruction that a remote peer must upload immediately. The queue guide explains why organisation and remote upload availability should be considered separately.

Keep a short record of destination rules

Record the category name, pattern and full output path. After one file completes, verify where it arrived and whether it appears in the expected shared-file view. That observation checks both the organisation rule and the storage result.

Include category-specific paths when you back up or move the installation. Restoring the category name without making its destination available can leave an otherwise healthy transfer unable to finish.

Sources and further reading

Some project help includes historical interface examples. Match the instructions to your installed build.

Keep going