01
Where it fits and where it does not
Use these four checks before committing implementation time.
- Use it when
- Session-level packaging and reuse of complex neurophysiology experiments where synchronized signals and experiment context must remain together.
- Limits
- Extensions and optional fields can fragment interoperability; storage and API compatibility must be tested, and schema validity does not establish signal quality or biological correctness.
- Best for
- Neuroscience and Laboratory and Imaging teams working across Acquire → Harmonize → Exchange → Learn + reuse.
- Maturity
- EstablishedSuitable for production assessment. Pin the exact release and any implementation profile.
02
See it in the workflow
This view shows the input, the change the standard introduces, and the resulting output.
- InputWhat starts
Neuroscience and Laboratory and Imaging source data, metadata, and local mappings
- NWBWhat changes
Use NWB as a pinned data model / schema across Acquire → Harmonize → Exchange → Learn + reuse
- OutputWhat becomes possible
A handoff the next system or team can validate against the same release
03
A concrete example
An electrophysiology study writes synchronized recordings, electrodes, stimuli, trials, processing modules, subject metadata, device models, and provenance to validated NWB files.
Why it matters: Standardized time series, events, trials, and device context enable reusable feature pipelines, while annotation quality, sampling bias, and split design remain project responsibilities.
04
What it fits with
The core schema is commonly serialized through HDF5; storage implementations must be pinned separately. BIDS provides complementary study-level organization, and DANDI validates supported NWB submissions.
- StandardBIDS
Both support Imaging and Neuroscience work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Metadata profileREMBI
Both support Imaging and Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaOME Model / OME-TIFF
Both support Imaging and Laboratory work and meet around Acquire, Harmonize, Exchange, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship - Data model / schemaOME-NGFF
Both support Imaging and Laboratory work and meet around Acquire, Harmonize, Learn + reuse. Compare their roles before treating them as interchangeable.
Explore relationship
05
Implementation starter
Start with one bounded handoff. Pin, test, and review it before scaling.
Define one handoff, its accountable owner, and the decision NWB must support.
Pin the exact version and companion artifacts: 2.10.0 · 2026-06-18.
Map one representative input to the required data model / schema artifacts.
Test the result against the canonical source and record every exception.
Preserve the source data, mappings, and review evidence before scaling.
06
Test the main limitation
Extensions and optional fields can fragment interoperability; storage and API compatibility must be tested, and schema validity does not establish signal quality or biological correctness.
Run one representative end-to-end pilot and record exactly where NWB loses context, needs an extension, or depends on another standard.
Machine-readable output may still be unfit for analysis or ML.
Test the output for missing context, provenance, terminology alignment, time leakage, and the intended downstream decision. Standardized time series, events, trials, and device context enable reusable feature pipelines, while annotation quality, sampling bias, and split design remain project responsibilities.
07
Official resources
Specifications, diagrams, examples, and guides from the organizations that maintain them.
NWB 2.10.0 format specification
Official publisher or steward guidance for this data model / schema profile.
- Publisher
- Neurodata Without Borders community