PlatformPCRegionNot confirmedVersionNot confirmed
The quick answer

The publisher overview distinguishes loadout-related advantages such as Perks, Add-Ons and Offerings. Read each current description in its own context rather than treating every Bloodweb purchase as a permanent ability.[1]

Official store screenshot for Dead by Daylight, image 2
Official store screenshot for Dead by Daylight, image 2. Promotional imagery for visual context.© Behaviour Interactive Inc. Official source ↗
On this page
  1. Understand the distinction
  2. Suggested checklist
  3. Limits and next steps

Understand the distinction

Our practice recommendation is to build a small loadout you can explain. It is easier to learn an interaction when you know which slot and item description it comes from.[1]

Suggested checklist

  1. Inspect each equipped item and identify its type and stated effect.[1]
  2. Choose one interaction to observe in a Trial rather than changing the full loadout each match.[1]
  3. Afterward, compare what happened with the current description before assuming a bug or hidden bonus.[1]

Limits and next steps

Consumption, compatibility and activation rules vary by item. No blanket persistence rule or best Perk build is supplied.[1]

Continue with Dead by Daylight cross-progression: linking and syncing.

A useful next step

Dead by Daylight cross-progression: linking and syncingDead by Daylight Bloodweb: spending Bloodpoints and levelingDead by Daylight Killer: learn a power and a chase
Check the original

Sources & verification

Facts last checked Oct 31, 2026. Checking a source does not change the page’s update date.

  1. Dead by Daylight: The Game | Gameplay, Story and Goals | Dead by Daylight Behaviour Interactive · official · Checked Oct 31, 2026

    Official documentation; check publication context and any later revisions.

    Original language: en
  2. Dead by Daylight — official Steam listing Behaviour Interactive Inc. / Valve · official · Checked Oct 31, 2026

    Steam desktop listing checked through Valve’s public appdetails API. Platform and requirements fields describe this storefront edition, not every console release.

    Original language: en

Page history

Published an original English source-linked explanation with scope limits and a suggested checklist.

Spotted something that needs a second look?

A source and a little context help us keep this guide useful.

Suggest a correction