In Opik 2.0, datasets are project-scoped. Make sure to specify a project_name when creating datasets so they are associated with the correct project.
Datasets can be used to track test cases you would like to evaluate your LLM on. Each dataset is made up of a dictionary
with any key value pairs. When getting started, we recommend having an input and optional expected_output fields for
example. These datasets can be created from:
Once a dataset has been created, you can run Experiments on it. Each Experiment will evaluate an LLM application based on the test cases in the dataset using an evaluation metric and report the results back to the dataset.
The simplest and fastest way to create a dataset is directly in the Opik UI. This is ideal for quickly bootstrapping datasets from CSV files without needing to write any code.
Steps:

If you need to create a dataset with more than 1,000 rows, you can use the SDK.
The UI dataset creation has some limitations:
For datasets requiring rich metadata, complex schemas, or programmatic control, use the SDK instead (see the next section).
When you create a dataset with a CSV file, this creates the first version (v1) of your dataset. All subsequent modifications will create new versions automatically.
Dataset versioning in Opik creates immutable snapshots of your data. Every time you modify a dataset—whether adding, editing, or deleting items—a new version is automatically created. This ensures complete reproducibility, provides an audit trail of all changes, and allows easy rollback to any previous state.
Each dataset version contains:
production, baseline)Once a version is created, its data cannot be changed—any modification creates a new version instead. Restoring a previous version also creates a new version with the same data, preserving your complete version timeline.
The special latest tag always points to the most recent version.
When running experiments without specifying a version, latest is used by default.
When making changes to a dataset in the Opik UI, all modifications go into a draft state first. This gives you a staging area to review changes before committing them as a new version. The draft is visible only to you, and AI-generated samples from “Expand with AI” also go to draft for review.
When a dataset has unsaved draft changes, an orange “Draft” tag appears next to the dataset name, and Save changes / Discard changes buttons appear in the toolbar. Items show colored borders: green for newly added items, amber for modified items.

To commit your draft as a new version:

To abandon your draft, click Discard changes and confirm. If you try to navigate away with unsaved changes, Opik displays a warning to prevent accidental loss of work.
Use draft mode to batch related changes into a single, well-documented version.
To view the complete timeline of dataset changes, navigate to your dataset and click the Version history tab. The table shows each version’s name, change summary (items added/modified/deleted), version note, tags, item count, and creation timestamp.

From this view you can:
Restoring a version creates a new version with the same data. No history is lost or overwritten.
The Dataset object exposes get_tags() to read the current tags, but does not yet provide a dedicated setter. To write tags programmatically — for example to drive an env:prod / env:stage promotion workflow — use the REST client exposed on the Opik client.
There are two tag surfaces, depending on what you want to scope the tag to:
update_dataset — this replaces the existing tag list.update_dataset_version — this is additive (it adds to the version’s existing tags).client.rest_client is a thin wrapper around the public REST API. The underlying endpoints are stable, but the Python wrapper itself is not guaranteed to be backward-compatible across SDK versions. A first-class Dataset.set_tags() / Dataset.add_version_tags() helper is on the roadmap — this snippet is the supported interim path.
You can then filter dataset items by these tags via get_items(filter_string=...) using the tags contains operator.
One of the most powerful ways to build evaluation datasets is by converting production traces into dataset items. This allows you to leverage real-world interactions from your LLM application to create test cases for evaluation.
To add traces to a dataset from the Opik UI:

By default, all metadata options are enabled. You can uncheck any options you don’t need. The trace’s input and output are always included.
When you add a trace to a dataset, the following structure is created:
expected_output for evaluation purposes)This rich structure allows you to:
In Opik 2.0, datasets are project-scoped. Specify a project_name to associate your dataset with the correct project.
You can create a dataset and log items to it using the get_or_create_dataset method:
If a dataset with the given name already exists, the existing dataset will be returned.
You can insert items to a dataset using the insert method:
Opik automatically deduplicates items that are inserted into a dataset when using the Python SDK. This means that you
can insert the same item multiple times without duplicating it in the dataset. This combined with the get or create dataset methods means that you can use the SDK to manage your datasets in a “fire and forget” manner.
When using the SDK to insert items, a new dataset version is automatically created.
If you insert items in multiple batches within a single insert() call, they are grouped into one version.
Once the items have been inserted, you can view them in the Opik UI:

You can also insert items from a JSONL file:
You can also insert items from a Pandas DataFrame:
You can delete items in a dataset by using the delete method:
Deleting items creates a new version of the dataset. The deleted items remain accessible in previous versions through the version history, ensuring you never permanently lose data.
You can download a dataset from Opik using the get_dataset method:
You can filter dataset items using the filter_string parameter on the get_items() method or when
running evaluations with evaluate_prompt(). This allows you to work with specific subsets of your data.
The filter string uses Opik Query Language (OQL) syntax. Supported columns include:
When you run an experiment, Opik automatically links it to the specific dataset version that was used. This ensures complete reproducibility—you can always know exactly which data was used for any experiment.
Every experiment records which dataset version it used:
latest version is usedThis association is permanent. Even if you later modify the dataset, your experiment results remain linked to the original version used.
When running experiments from the Playground:
latest for the most recent
When comparing experiments or running A/B tests, use the same dataset version to isolate the effect of your changes. This ensures differences in results are due to your prompt or model changes, not data variations.
When running experiments programmatically, you can specify which dataset version to use by passing a DatasetVersion object to evaluate():
The SDK provides methods for inspecting and working with dataset versions:
DatasetVersion is a read-only view. You cannot insert, update, or delete items
through a DatasetVersion object. All mutations must be done through the Dataset object.
Dataset expansion allows you to use AI to generate additional synthetic samples based on your existing dataset. This is particularly useful when you have a small dataset and want to create more diverse test cases to improve your evaluation coverage.
The AI analyzes the patterns in your existing data and generates new samples that follow similar structures while introducing variations. This helps you:
To expand a dataset with AI:

Sample Count: Start with a smaller number (10-20) to review the quality before generating larger batches.
Preserve Fields: Use this to maintain consistency in certain fields while allowing variation in others. For example, preserve the category field while varying the input and expected_output.
Variation Instructions: Provide specific guidance such as:
Dataset expansion works best when you have at least 5-10 high-quality examples in your original dataset. The AI uses these examples to understand the patterns and generate similar but varied content.
Tags are a powerful way to organize, categorize, and filter your dataset items. You can use tags to:
edge-case, production, multilingual)user-feedback, synthetic, real-world)needs-review, validated, archived)Each dataset item can have multiple tags.
To add tags to a single dataset item:
You can remove tags by clicking the ”×” icon next to any tag in the details panel.
To add the same tag to multiple dataset items at once:
This is particularly useful when you want to categorize a group of related test cases or mark items from the same data source.
Tags are case-sensitive and support alphanumeric characters, hyphens, and underscores. Choose consistent naming conventions for your tags to make filtering easier.
Once you’ve tagged your dataset items, you can filter them to work with specific subsets:
The dataset items table will update to show only items matching your filter criteria. You can:
The filter is saved in the URL, so you can bookmark or share specific filtered views of your dataset.
Opik supports bulk operations for efficiently managing large datasets. These operations help you work with many items at once without tedious individual selections.
When working with datasets that span multiple pages:

This works with filtered views too—if you have a filter applied, “Select all” only selects items matching that filter.
Once you have items selected, the toolbar shows available operations:
For large bulk operations:
For very large datasets, bulk operations are processed in batches. The UI remains responsive during processing, and you’ll see progress indicators for long-running operations.