BTW File Documentation

Summary

A BarTender Label Document (.btw) is the native design file of BarTender, the barcode and label software from Seagull Scientific. It stores one label template: its dimensions, the barcode, text and image objects on it, and the rules that pull variable data from a database or spreadsheet at print time. The format is proprietary, so only BarTender opens it; its generic MIME type is application/octet-stream. If you lack BarTender, ask the sender for an exported PDF or PNG.

Technical details

Feature	Value
Full name	BarTender Label Document
File extension	`.btw`
MIME type	`application/octet-stream`
Format type	Proprietary binary label-design document
Developer	Seagull Scientific
Application	BarTender (Windows only)
Introduced	1990s (Seagull Scientific founded 1985)
Open standard	No — layout not publicly documented
Container (older versions)	Microsoft OLE Compound File Binary
Magic number (older CFB files)	`D0 CF 11 E0 A1 B1 1A E1`
Byte order	Little-endian (CFB header)
Stores	Label geometry, barcode/text/image objects, data-source bindings, RFID setup
Barcode symbologies	Code 128, GS1-128, QR Code, Data Matrix, and others
Data sources	Database, CSV/Excel, or keyboard/prompt entry
Companion format	`.btxml` (XML export for integration)
Related extensions	`.btxml`, `.pdf`, `.png`, `.jpg`
Vendor site	`bartendersoftware.com`

File signature (magic bytes)

D0 CF 11 E0 A1 B1 1A E1

Offset 0, 8 bytes — but only for older .btw files. BarTender historically saved its label documents as a Microsoft OLE Compound File Binary (the same container structure once used by legacy .doc and .xls), which begins with this signature. Seagull Scientific has never published the internal layout, and newer BarTender releases may use a different container, so there is no single reliable constant that identifies every .btw. Treat the extension as BarTender-specific and identify it by association with the software, not by a fixed magic number. This is unrelated to the old Bluetooth .btw stack files some drivers wrote.

What is a BTW file?

A .btw file is a BarTender Label Document: the native, editable design file produced by BarTender, the label and barcode software made by Seagull Scientific. Seagull Scientific was founded in 1985 in the United States, and BarTender itself dates to the 1990s. The application is used across manufacturing, logistics, retail, healthcare and supply-chain operations to design and print product labels, shipping labels, barcodes and RFID tags. A single .btw holds one label template, not a finished picture of a label: it records the design plus the logic that fills it with data at print time, so one file can generate thousands of different labels from a database.

The format is proprietary and closed. Seagull Scientific does not publish the byte layout of a .btw, and no mainstream image viewer, office suite or free utility renders it correctly. That single fact drives almost every practical question about the extension: you cannot open a .btw without BarTender, and there is no legitimate third-party viewer. What follows is what is actually known about the file, and how to work with it honestly.

The OLE Compound File container

Older versions of BarTender saved .btw documents as a Microsoft OLE Compound File Binary (CFB), also called a Compound Document or “structured storage” file. This is the same container that legacy Microsoft Office used for .doc and .xls before the XML-based formats arrived. A CFB is effectively a small file system inside a single file: it presents a tree of named storages (directories) and streams (files), so an application can store many separate pieces of structured data in one document without inventing its own container.

Because of that container, an older .btw begins with the CFB signature at offset 0:

Offset 0:  D0 CF 11 E0 A1 B1 1A E1     CFB / OLE2 magic (8 bytes)
Offset 8:  ...                         CLSID, minor/major version
Offset 24: FE FF                       byte-order mark (little-endian)
...        512-byte header, then FAT/directory sectors

Those first eight bytes (sometimes nicknamed the “magic docfile header”) tell a parser it is looking at a compound document. What they do not tell you is anything about BarTender’s own schema: the names and contents of the internal streams that hold the label design are private to Seagull Scientific and are not documented. So while a generic CFB tool can list the storages and streams inside an older .btw, it cannot interpret them into a label. Newer BarTender releases may use a different container entirely, which is why no single magic number reliably identifies every .btw in the wild. The reliable identifier is context: the file came from, or is meant for, BarTender.

What a label template stores

Conceptually, regardless of the container, a .btw describes one label as a set of objects placed on a defined page. The design breaks down into a few kinds of content:

Element	What it holds
Template geometry	Page size, orientation, label dimensions, margins and how many labels sit across a sheet or roll
Barcode objects	The symbology (Code 128, GS1-128, QR Code, Data Matrix and others), the encoded data, and the human-readable text line
Text and shape objects	Fixed and variable text, lines, boxes, and embedded images or logos
Data-source bindings	Links that connect fields to a database, a CSV/Excel file, or a prompt so variable data is filled at print time
RFID encoding setup	Tag type and the data to write to an RFID inlay, where the label uses one

The data-source binding is the part that makes BarTender more than a drawing tool. A field on the label is not a static string; it is a reference that BarTender resolves against a connected data source each time it prints. Feed the template a 10,000-row spreadsheet and it emits 10,000 labels, each with its own product name, price and barcode, from the one .btw. That is also why a shared production template can be sensitive: the file can embed connection details for a label database.

Printing, and why export is one-way

Because the design and its data logic live together in a proprietary file, the only faithful way to render a .btw is to let BarTender do it. BarTender runs on Windows only and is sold in editions (Starter, Professional, Automation, Enterprise), with a time-limited free trial that is enough to open a one-off file, view it, and export it.

Exporting is the realistic route to sharing a label with someone who does not have BarTender. Open the .btw in BarTender and print or export to PDF for a fixed, printable proof, or to PNG for a preview image. Prefer PNG over JPG for barcodes: JPEG’s lossy compression can blur the bars enough to break a scan, while PNG’s lossless output keeps the edges crisp. Every one of these exports is one-way. A PDF or PNG is a flattened snapshot; it drops the object model and the data-source bindings, so you cannot convert it back into an editable .btw. There is likewise no meaningful conversion to Word or a spreadsheet, because a label template is not a text document. For integration workflows, BarTender also has a companion XML export, .btxml, which represents template data in a structured, machine-readable form.

References

Feedback

Was this page helpful?

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.

Table of contents