For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Access feature previews
  • How feature previews work
  • Best practices
  • Benefits
Your account

Feature previews

Was this page helpful?
Previous

Billing and usage

Next
Built with
Feature previews are available to eligible LaunchDarkly accounts

Feature previews are available to eligible LaunchDarkly accounts. If your organization has access, your account team notifies you when new previews become available.

Overview

This topic explains how to use feature previews in LaunchDarkly to access upcoming capabilities early. Feature previews help your teams prepare for new features, test updates safely, and build confidence that product changes do not disrupt existing workflows.

They are especially useful for large or complex organizations that need to evaluate new behavior in a controlled environment. Enabling a feature preview lets your teams explore updates and provide input to LaunchDarkly before general availability.

Access feature previews

To access available feature previews:

  1. Click your profile picture in the lower-left corner of LaunchDarkly.
  2. In the menu, choose Feature preview.

A dialog appears that lists all available feature previews for your account. Each preview includes a short description of what it changes.

Toggle the switch next to a feature’s name to enable or disable it. Changes take effect immediately for your account.

How feature previews work

Feature previews are managed at the organization level. When you enable a preview, all members of your organization can use the feature.

LaunchDarkly provides feature previews ahead of general availability so customers can explore new functionality and share feedback. This lets you:

  • Test new functionality in your own environment.
  • Offer feedback to your account team.
  • Prepare internal documentation or training before a new feature launches.
  • Validate compatibility with your internal tools and workflows.

Best practices

Follow these best practices to get the most value from feature previews:

  • Assign reviewers who can evaluate the feature’s impact and communicate findings.
  • Use a non-production environment to confirm expected behavior.
  • Record feedback and share it with your LaunchDarkly account team.
  • Disable previews when testing is complete to return to the standard experience.

Benefits

Feature previews help your organization:

  • Gain early insight into upcoming platform changes.
  • Reduce surprises when new features reach general availability.
  • Influence feature design and usability through early feedback.
  • Plan adoption and training timelines in advance.