# AI use cases for Label Studio (HumanSignal/label-studio)

Repo: [HumanSignal/label-studio](https://github.com/HumanSignal/label-studio) | Use cases: 3 | Page: https://dedupedai.com/use-cases/humansignal-label-studio/

Label Studio is an open source data labeling tool for audio, text, images, video, HTML and time series. It provides configurable labeling templates, multi-user projects, imports from files or cloud storage such as S3 and Google Cloud Storage, export to model formats, a REST API for pipelines, and an ML backend SDK so models can pre-label data and support online and active learning.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Start labeling images, text or audio locally: https://dedupedai.com/use-cases/humansignal-label-studio/start-labeling-data-locally-in-minutes/
- Speed up labeling by pre-labeling with your own model: https://dedupedai.com/use-cases/humansignal-label-studio/pre-label-data-with-your-model/
- Run a shared labeling server for a team: https://dedupedai.com/use-cases/humansignal-label-studio/run-a-team-labeling-server-with-docker-compose/

## How to start labeling images, text or audio locally with Label Studio

Repo: [HumanSignal/label-studio](https://github.com/HumanSignal/label-studio) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Run Label Studio with Docker or pip and open a labeling UI at localhost:8080.

**Who it is for:** A data scientist who needs a few hundred labeled images or text samples for a first model.

**The problem:** Labeling in spreadsheets or ad hoc scripts is slow, error prone and hard to export to training formats.

**The outcome:** A local labeling server with your project, data stored in a folder you control and exports in model formats.

### Steps

1. Run `docker pull heartexlabs/label-studio:latest`
2. Start it with `docker run -it -p 8080:8080 -v $(pwd)/mydata:/label-studio/data heartexlabs/label-studio:latest`
3. Or install with `pip install label-studio` and run Label Studio
4. Open localhost:8080, create a project and pick one of the included templates for your data type
5. Label your data and export it to the format your training code needs

### Prompt to paste into your agent

```text
Start HumanSignal/label-studio locally with Docker using a mydata folder for storage, then tell me which included template fits <labeling task> and how to import <dataset> into a new project.
```

### Caveat

The default setup uses SQLite in the mydata folder, which suits small projects; use Docker Compose with PostgreSQL for a team.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/humansignal-label-studio/start-labeling-data-locally-in-minutes/

## How to speed up labeling by pre-labeling with your own model with Label Studio

Repo: [HumanSignal/label-studio](https://github.com/HumanSignal/label-studio) | Difficulty: Advanced | Time: 2 hours | Basis: From the README

Connect an ML backend so Label Studio fills in model predictions and annotators only correct them.

**Who it is for:** An ML team with a first model that is decent but not good enough, and thousands of items left to label.

**The problem:** Labeling every item from scratch is slow when a model could already get most of them right.

**The outcome:** Tasks arrive with model predictions filled in, so annotators review and fix instead of starting from zero.

### Steps

1. Start your own machine learning backend server with the Label Studio ML backend
2. In project settings, open the model page and connect Label Studio to the server
3. Turn on pre-labeling so tasks show model predictions
4. Use active learning to label only the most complex examples first
5. Retrain with online learning as new annotations come in

### Prompt to paste into your agent

```text
Set up a HumanSignal/label-studio ML backend for my <model type> model so it pre-labels tasks in project <name>. Explain how to connect it on the model page and how to compare its predictions with annotator labels.
```

### Caveat

Pre-labels can bias annotators toward the model's mistakes, so review a sample of accepted predictions.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/humansignal-label-studio/pre-label-data-with-your-model/

## How to run a shared labeling server for a team with Label Studio

Repo: [HumanSignal/label-studio](https://github.com/HumanSignal/label-studio) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

Use the Docker Compose stack with Nginx and PostgreSQL for multi-user labeling.

**Who it is for:** A team lead coordinating several annotators across multiple datasets.

**The problem:** Passing files around and merging labels from several people leads to lost and conflicting work.

**The outcome:** One server where every annotation is tied to a user account, with multiple projects and cloud storage imports.

### Steps

1. From a checkout of the repo, run `docker-compose up` to start Label Studio, Nginx and PostgreSQL
2. Open the app at localhost and have each annotator sign up so their annotations are tied to their account
3. Create one project per dataset and import from files or cloud storage such as Amazon AWS S3 or Google Cloud Storage
4. For local S3 testing, run `docker compose -f docker-compose.yml -f docker-compose.minio.yml up -d`
5. Use the REST API to pull finished annotations into your training pipeline

### Prompt to paste into your agent

```text
Deploy HumanSignal/label-studio with the Docker Compose stack on <server>, connect project <name> to my <S3 or GCS bucket>, and write a script that uses the REST API to export completed annotations nightly.
```

### Caveat

If the server is reachable from the internet, put it behind HTTPS and restrict sign ups to your team.

Risk, credentials: Connecting cloud storage means giving Label Studio bucket credentials; use a key scoped to just the labeling bucket.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/humansignal-label-studio/run-a-team-labeling-server-with-docker-compose/
