Skip to main content
Use Notebooks to create interactive, reactive Python notebooks inside W&B. Notebooks are useful for exploring data, prototyping model workflows, analyzing W&B runs and artifacts, and sharing reproducible work with collaborators. Notebooks use marimo as the notebook runtime and editor. Unlike traditional notebooks that run from top to bottom, Notebooks track dependencies between cells. When a value changes, the notebook can identify the downstream cells that depend on it and keep outputs consistent with the current notebook state.

​
Get started

If you are new to notebooks, start with the Get started guide. The guide walks you through creating a notebook, running code, viewing logged metrics in a W&B workspace, and sharing the result. If you already know the workflow you want, use the following pages:

Create and manage notebooks

Create, rename, duplicate, or delete notebooks from a team overview page or project workspace.

Edit a notebook

Add Python, Markdown, and SQL cells; reorder cells; delete cells; and add interactive controls.

Run notebook cells

Run stale cells, rerun every cell, stop a running cell, disable execution, or restart the runtime.

Manage packages

Install, view, update, and remove Python packages from the notebook sidebar or terminal.

​
Understand the notebook model

Notebooks are reactive. A cell runs based on the variables it defines and references, not only on where it appears in the notebook. This model helps keep outputs current, but it also means that notebook structure matters:
  • Define each global name in only one cell.
  • Avoid mutating shared objects across cells.
  • Use runtime settings to choose whether downstream cells run automatically or become stale.
  • Use the dependency tools to inspect how cells relate to each other.
For a deeper explanation, see Understand reactive execution and Configure a notebook.

​
Debug and inspect notebooks

Use the developer panel to investigate notebook behavior without leaving the editor. The panel includes errors and warnings, a scratchpad for temporary code, execution traces, logs, and a terminal connected to the notebook workspace. For details, see Developer tools.

​
Billing and usage

Notebooks use W&B storage and sandbox compute. Notebook data contributes to your organization’s storage usage, while running a notebook consumes sandbox compute. Notebook workflows can also create product-specific usage when they call other W&B services such as Weave, Inference, or Training. Organization and billing admins can review plan details, monitor usage, configure usage and spending alerts, manage payment methods, and access invoices from Billing settings. For plan and pricing information, see W&B Pricing. If your account does not have sufficient storage or sandbox capacity, you may need to free storage, purchase additional usage, upgrade your plan, or contact W&B Sales.

​
Next steps