Common billing tasks
Manage billing details
Update account plan
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. Catalog LBUs are charged each month while Annotate and Model are one-time charges. 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 | 1 LBU per 60 data rows | 1 LBU per data row | 1 LBU per 5 data rows |
| Text | 1 LBU per 60 data rows | 1 LBU per data row | 1 LBU per 5 data rows |
| Chat (Conversation) | 1 LBU per 60 data rows | 1 LBU per data row | 1 LBU per 5 data rows |
| Audio | 1 LBU per 60 data rows | 1 LBU per data row | 1 LBU per 5 data rows |
| Document (PDF), per page | 1 LBU per 60 data rows + 1 LBU per 60 pages | 1 LBU per page | 1 LBU per 5 pages |
| Video | 1 LBU per 60 data rows + 1 LBU per 5,000 frames | 1 LBU per 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 rows | 4 LBU per data row | 1 LBU per data row |
| Multi Modal/LLM | 1 LBU per 60 data rows | 20 LBU per data row | 1 LBU per 5 data rows |
Skipped data rows
For Annotate projects, skipped data rows are considered labeled and contribute to LBU.LBU consumption
Different actions within Labelbox consume LBUs. Here’s how consumption works for each Labelbox productCatalog 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.
Annotate consumption
In Annotate, LBUs are consumed when:- Labels are submitted to a project.
Model consumption
In Model, LBUs are consumed when you:- Add data rows to a model run.
- Use Foundry to create and submit model predictions.
- Use data rows for model-assisted labeling (MAL), either through the app or the SDK.
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
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
- Plans and pricing for current pricing, an estimate calculator, and answers to questions frequently asked by new customers.
- Pricing updates (blog) for a description of the Feb 2024 pricing change and additional details for existing customers.
- View account details to view LBU consumption for the current billing period.
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.
- Labeling services connect you with labelers with specialized knowledge to annotate and review large amounts of data for you. For Enterprise accounts, the service is included in your plan and fully managed. For Starter and Free accounts, you hire your team a week at a time per project. Each week is billed and paid separately from your subscription.
- 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.