---
title: "Features"
description: "Control which Verifier2 API features are enabled using _features.conf."
stack: "Community Stack (open source) — version 0.21.0"
stack_version: "0.21.0"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/community-stack/verifier2/configurations/config-files/features
generated: 2026-07-20
---
# Features

With `_features.conf` you can control which Verifier2 API features are enabled. They are managed via
the [feature manager](https://docs.walt.id/community-stack/verifier2/configurations/feature-manager.md).

## Available Features

### Base Features

Base features are always enabled. They do not need to be listed in `_features.conf`.

- `verifier-service` — Core verification service implementation. Handles verification session creation,
  authorization request generation, and VP response processing.

### Optional Features

- `dev-mode` — Development mode. Disabled by default. When enabled, loads additional settings from
  `dev-mode.conf` (e.g. allows DID Web resolution over plain HTTP). See
  [dev-mode.conf](https://docs.walt.id/community-stack/verifier2/configurations/config-files/dev-mode.md) for details.
- `transaction-data-profiles` — Transaction-data type registry and discovery endpoint. Enabled by default. Loads
  `transaction-data-profiles.conf` and exposes `GET /transaction-data-profiles`. See
  [transaction-data-profiles.conf](https://docs.walt.id/community-stack/verifier2/configurations/config-files/transaction-data-profiles.md) for details.

## Example Setup

```editorconfig[_features.conf]
enabledFeatures = [
    dev-mode
]
disabledFeatures = [
    # ...
]
```