Manage account and billing

Learn how to perform common billing tasks and how Labelbox charges works.

This topic helps you find how to perform common billing tasks, outlines how Labelbox handles billing, and points you to more information.

Common billing tasks

Labelbox units (LBUs)

A Labelbox Unit (LBU) is a normalized unit of data in the Labelbox platform.

Each LBU represents work performed using one or more data rows. Each Labelbox product (Catalog, Annotate, and Model) performs different tasks.

As a result, LBU charges vary according to the product, the amount and type of data processed, and what you do with it:

Data row
asset type
Catalog
(monthly)
Annotate
(one-time)
Model
(one-time)
Image
Text
Chat (Conversation)
JSON
Audio
Document (PDF), per page
1 LBU per 60 data rows1 LBU per labeled data row1 LBU per 5 data rows
Video1 LBU per 60 data rows
+
1 LBU per 5,000 frames
1 LBU per labeled data row
+
1 LBU per 150 frames
1 LBU per 5 data rows
+
1 LBU per 1,500 frames
Geospatial &
Medical Tiled Imagery
1 LBU per 6 data rows4 LBU per labeled data row1 LBU per data row
DICOM1 LBU per 6 data rows2 LBU per labeled data row1 LBU per 2 data rows

Catalog LBUs are charged each month while Annotate and Model are one-time charges.

Free accounts have 500 free LBU credits each month. If you reach this limit, you can access and export your data. However, you cannot add data rows, labels, or predictions until the next billing period. (You can upgrade your account at any time.)

This table became effective February 1, 2024. To learn more, see Pricing updates.

LBU consumption

Different actions within Labelbox consume LBUs. Here's how consumption works for each Labelbox product

Catalog consumption

In Catalog, LBUs are consumed when you upload data into Catalog, regardless of the data type.

To safeguard against unintended uploads, there is a seven (7) day grace period when you first upload data. If, during that time, you remove unused data rows before the grace period expires, no LBUs are consumed.

However, if you perform an action that adds labels to a data row, the row consumes LBUs, even within the grace period.

Once the grace period expires, data rows consume LBUs.

After the grace period, Catalog LBU consumption applies to the entire billing period. While you can delete data rows at any time, LBU consumption is not updated until the next billing period.

To illustrate, suppose you upload 600 images to a dataset:

  • For the first seven days after the initial upload, no LBUs are consumed. You can delete as many rows as you like.
  • If you label 60 rows within the grace period, those rows consume 1 LBU for the current billing period, even if you delete them after labeling them.
  • Once the grace period expires, the remaining 540 data rows consume 9 LBUs in the current billing period.
  • If you delete 300 rows after the grace period, you are charged 10 Catalog LBUs in the current billing period. In the next billing period, Catalog LBU consumption drops to 5 LBU to reflect the remaining data row count.

Remember, each product consumes LBUs. If you used Annotate to label the initial 60 rows in the previous example, this would have consumed 60 LBUs. To learn more, see the next section.

Annotate consumption

In Annotate, LBUs are consumed when:

  • Labels are approved as ground truth by a reviewer, whether initially generated manually or as Foundry predictions.
  • Review tasks are marked as Done (without review).

Annotate LBUs are one-time charges.

Model consumption

In Model, LBUs are consumed when you:

  • Add labeled data rows to a model run in an experiment.
  • Use Foundry to create and submit model predictions.

Model LBUs are one-time charges.

Be aware that Foundry may incur additional inference costs based on the number of rows processed, the complexity of the task, the model used, and other factors. To learn more, see Add-on charges.

LBU examples

The following examples illustrate LBU consumption for common workflows.

Data labeling using model-assisted pre-labels

Imagine you need to label 1,000 images and that half of your images have pre-labels generated by Foundry. In this scenario, you would be charged as follows:

  • Catalog: 17 LBU per month for 1,000 data rows (200 LBU annually)
  • Model: 100 LBU for predictions on 500 data rows, charged once
  • Annotate: 1,000 LBU for 1,000 labeled data rows, charged once

If this activity occurred within a single billing period, you would be charged 1,117 LBU once and 1.67 LBU each month the data rows remain in Catalog.

Data curation and labeling with enrichment

Imagine you have 60,000 images with Foundry predictions and that 10,000 of these images are labeled:

  • Catalog: 1,000 LBU per month for 60,000 data rows (or 12,000 LBU annually)
  • Model: 12,000 LBU for 60,000 data rows with a prediction, charged once
  • Annotate: 10,000 LBU for 10,000 labeled data rows, charged once

If this activity occurred with the same billing period, you would be charged 23,000 LBU once and 1,000 LBU each month the data remains in Catalog.

To learn more, see:

Add-on charges

Your account may also be billed for add-on services. These charges are billed separately from your subscriptions and may require that you add a credit card to your account. (Specific requirements vary according to your subscription and the add-on.)

Available add-ons include:

  • Foundry, which uses foundational models to predict labels and enrich data, incurs inference costs. When you perform a model run, a fee is charged based on the amount of data involved, the model used, the complexity of the inference task, and other factors. To use Foundry, you need to accept these charges and have a valid payment method associated with your account. To learn more, see Foundry billing.

  • Boost Express lets Starter and Free accounts hire a human labeling team to help label data. When using Workforce Boost Express, you hire your team a week at a time. Each week is billed and paid separately from your subscription.

  • Boost Workforce lets Enterprise subscribers hire a human labeling team.

  • Sign sign on (SSO) lets Enterprise teams use their single sign-on service to sign in to Labelbox.

  • HIPAA helps Enterprise subscribers comply with the Health Insurance Portability and Accountability Act of 1996 and related regulations.

Enterprise customers should contact their technical account manager to verify terms, payment, and other details for their add-ons.

To learn more about available add-ons, see Plans and pricing.