---
title: Converting data
description: Move between loaders.gl data shapes with explicit, composable converters.
hide_title: true
page_style: designed
---
import {DocPageHeader} from '@site/src/components/docs/doc-page-header';
import {ConversionPipelineGraphic} from '@site/src/components/docs/conversion-pipeline-graphic';
import {DocOrientation, ReferenceBoundary} from '@site/src/components/docs/designed-doc';
The loaders.gl converter system is a graph of small, explicit converter objects. You pass the converters you want, `convert()` finds a path, and each leaf module handles one direct step.
```ts
import {convert, TableConverter} from '@loaders.gl/core/schema-utils';
import {ArrowConverter} from '@loaders.gl/tables/arrow';
import {
FeatureCollectionConverter,
GeometryConverter
} from '@loaders.gl/core/geoarrow';
const arrowTable = convert(table, 'arrow', [TableConverter, ArrowConverter]);
const wkb = convert(geometry, 'wkb', [GeometryConverter]);
const binary = convert(features, 'binary-feature-collection', [FeatureCollectionConverter]);
```

## In This Section
| Topic | Use it for |
| --- | --- |
| [Converter dispatcher](/docs/developer-guide/converters/dispatcher) | How `convert()` detects shapes and chooses a path |
| [Table and Arrow converters](/docs/developer-guide/converters/table-and-arrow-converters) | Moving between loaders.gl table wrappers and Apache Arrow |
| [GeoArrow converters](/docs/developer-guide/converters/geoarrow-converters) | Converting GeoArrow tables and rewriting GeoArrow geometry encodings |
| [Feature collection converters](/docs/developer-guide/converters/feature-collection-converters) | GeoJSON, Flat GeoJSON, binary feature collections, and geometry wire formats |
| [Render converters](/docs/developer-guide/converters/render-converters) | Direct geometry-column to `BinaryFeatureCollection` and Arrow-backed binary wrappers |
| [Format categories](/docs/developer-guide/converters/format-categories) | The shapes and format families these converters connect |
## Core Ideas
- Converters are opt-in. There is no global registry.
- Each leaf converter handles direct edges only.
- `convert()` can compose multiple direct steps when you pass enough converters.
- Geometry rendering does not have to route through GeoJSON.
## Current Converter Families
| Converter | Package | Direct responsibility |
| --- | --- | --- |
| `TableConverter` | `@loaders.gl/core/schema-utils` | loaders.gl table wrappers |
| `ArrowConverter` | `@loaders.gl/tables/arrow` | Native Arrow and row, columnar, or GeoJSON tables |
| `GeoArrowTableConverter` | `@loaders.gl/core/geoarrow` | Native GeoArrow and row, columnar, or GeoJSON tables |
| `GeoArrowGeometryConverter` | `@loaders.gl/core/geoarrow` | GeoArrow geometry encoding rewrites |
| `FeatureCollectionConverter` | `@loaders.gl/core/geoarrow` | GeoJSON, Flat GeoJSON, binary feature collections |
| `GeometryConverter` | `@loaders.gl/core/geoarrow` | single geometry values like WKB, WKT, TWKB, GeoJSON geometry |
## Render-Focused Conversions
Some conversions are not expressed as generic converter objects because they are rendering utilities rather than shape-dispatch nodes.
These include:
- `convertGeometryColumnToBinaryFeatureCollection()`
- `convertGeometryValuesToBinaryFeatureCollection()`
- `convertBinaryFeatureCollectionToArrowBinaryFeatureCollection()`
- `convertArrowBinaryFeatureCollectionToBinaryFeatureCollection()`
These utilities are documented in [Render converters](/docs/developer-guide/converters/render-converters).
## Why This Matters
The converter system gives you a few practical wins:
- small bundles through explicit imports
- predictable conversion paths
- reusable format-specific code in leaf modules
- a clean separation between table conversion, geometry conversion, and render conversion
The rest of this section goes converter by converter and shape by shape.