Experimental Features

Experimental Features explains how to test unstable capabilities deliberately and avoid relying on them in production profiles.

Overview

Experimental features are not guaranteed to behave the same across versions. They are useful for testing new capabilities but should be enabled deliberately.

Best practice

Enable one experimental option at a time, write down the original profile state, and keep a rollback path. Do not combine several new features while troubleshooting.

Production use

If the device is used for work, remote access or family members, prefer stable features first. Experimental options are better tested on a secondary profile.

Support Checks

When a regression appears after an update, disable experimental options first before changing rules, DNS or subscription providers.

Reference examples

These examples mirror the corresponding Chinese documentation page so the English page carries the same configuration material.

experimental:
  sniff-tls-sni: true