
A bundle file's presence does not prove that its Krita resources are active and visible. Check the bundle in Manage Resource Libraries, then check whether the individual brush was deactivated or hidden by a resource filter. Preserve the existing resource cache while diagnosing these states.
Key Takeaways
- Library activation and individual resource deactivation are separate.
- Show Deleted Resources and Undelete Resource can restore a deactivated item.
- Deleting the resource cache removes the tags and relationships it records.
Confirm import before changing the installation
Suppose a colleague supplies a brush bundle for a commercial illustration. The file is on disk, but the expected presets are missing from the brush chooser. Start with the resource manager rather than copying the file into guessed folders.
Open Settings > Manage Resource Libraries and look for the intended bundle. If it has not been imported, use Import, select the .bundle file and confirm it appears in the library list. Inspect its activation state using the library controls.
The Krita Resource Management reference distinguishes resource libraries from their individual resources. Reimporting the same library repeatedly does not establish that every contained preset is active.
Check the resource and the chooser separately
Open Settings > Manage Resources. Enable Show Deleted Resources to inspect deactivated items. If the intended resource is present in that state, select it and use Undelete Resource where restoration is appropriate.
Then inspect the brush chooser's active tag and search filter. Krita resources can belong to multiple tags, and resource selectors can filter by names or tags. Clear an unintended filter before concluding that the library lacks the item.
Keep these observations separate:
| Observation | Next state to inspect |
|---|---|
| Bundle absent from the library list | Import status |
| Bundle listed but resources unavailable | Library activation |
| Specific item appears only among deleted resources | Individual deactivation |
| Item exists in management but not the chooser view | Current chooser filter or tag |
Verify usability without discarding resource metadata
Select the restored preset and make a small mark in a disposable practice document. Confirm its identity and expected brush behavior, rather than accepting a similarly named replacement.
The manual says Krita's SQLite resource cache stores tags, names, versions and relationships, and deleting it removes the recorded tags and relationships. That makes cache deletion an unsuitable first response to a simple activation or filtering problem.
Accept the repair when the intended preset is visible and usable while existing custom organization remains identifiable. For a shared workflow, record the actual bundle and preset rather than merely saying “brushes installed.”
The recorded-action dependency guide covers a separate downstream issue: automation depending on a named brush. Resolving Krita visibility alone does not certify another application's preset dependencies.
Related tasks
- Why Does a Shared Photoshop Action Paint With a Different Brush?
- How to Find and Verify a Swatch in a Crowded Krita Palette
- Should Krita Reference Images Be Embedded Before Sending a KRA File?
Sources and scope
- Resource Management: Manage Resource Libraries imports and deactivates bundles. Individual resources can be deactivated separately and restored through Manage Resources > Show Deleted Resources > Undelete Resource. The resource cache stores tags and relationships, which cache deletion removes.
Official documentation synthesis; no hands-on test, search-volume or measured citation-rate claim. Scenarios and comparisons are proposed editorial examples, not reported experiments.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.