Book Spine Label Generator
Format existing Dewey, Library of Congress, Koha or local call numbers into measured printable spine-label sheets with batch import, copy lines, stamps, custom typography and start-position control.
Accuracy note: The tool deterministically formats the supplied text and validates the configured print geometry, but Dewey, Library of Congress, NLM and local classification correctness remains a cataloguing decision. Auto, Dewey and LC modes are transparent printing heuristics; use Preserve mode when your local line breaks are authoritative.
How this result is calculated and when to review it
Method: Formats supplied item call numbers into reviewable spine-label lines using user-selected Dewey, Library of Congress, automatic or preserve-line-break modes, combines optional copy/stamp text, validates the configured character and line guides, then lays the labels onto measured paper geometry before browser-side print or export. The formatting rules are printing heuristics and do not certify classification correctness.
Result type: Rule-based / deterministic.
Good practice: keep one known-good example, test small batches first, and document any local conventions that affect the result.
Worked example
Use a small representative input in Book Spine Label Generator, review the output and warnings, then repeat the process with real data only after the result matches your expected workflow.
Tip: the Try example control in the tool uses the built-in sample/default values so you can see the expected workflow before entering your own data.
A book spine label turns a catalogue call number into a small, readable physical label that helps staff and readers return an item to the correct shelf. The VWS Online Book Spine Label Generator is designed for that practical processing step. You can type one call number, paste a batch, or import CSV, TXT or Excel data, then control how the call number is broken into lines and how those labels are placed on A4, Letter, Legal or custom label stock.
This tool is intentionally different from a barcode generator. A barcode usually represents a machine-readable item identifier used for circulation or inventory. A spine label normally displays a human-readable classification or local shelf mark. A single book may therefore have a call number on the spine, a barcode elsewhere on the item, an accession number in the register and several internal database identifiers. Keeping those roles separate makes cataloguing, migrations and replacement-label work easier to audit.
What the Book Spine Label Generator does
The generator focuses on formatting and printing call-number text that already exists. It does not assign a Dewey Decimal Classification number or create an authoritative Library of Congress call number from a title. Instead, it takes the call number you supply and prepares a physical label layout. That distinction matters because classification depends on schedules, editions, shelflisting rules, local policy and professional cataloguing judgment.
You can use the tool for one-off labels, replacement labels, new-book processing, retrospective relabelling and migration cleanup. The revised workflow supports a single call number, a one-per-line pasted list and batch files in CSV, TXT, XLSX or XLS format. For spreadsheet data, you can map a call-number column plus optional copy-number, top-stamp, bottom-stamp and number-of-copies columns.
Book spine label vs barcode label
A spine label answers the shelving question: where does this item belong? A barcode usually answers the system question: which exact item is being scanned? For example, a book might have the call number QA76.73.J38 2026 on its spine and the barcode BK00045821 inside the cover. Those values should not be merged simply because both appear on labels.
If you need to create a new sequential Koha item barcode range, use the Koha Barcode Generator. If the identifiers already exist and you need a page of scannable labels or QR codes, use the Library Barcode Sheet Generator. This page is specifically optimized for narrow call-number and shelf-mark labels.
Using Koha call numbers for spine labels
In the standard Koha MARC21 item mapping, 952$o is the full item call number and maps to the item call-number field. Koha also uses 952$t for the copy number. The current Koha manual explains both fields in its cataloguing documentation and allows the item call number to be populated from a bibliographic call-number field according to the itemcallnumber system preference. See the official Koha cataloguing manual for the current installation-specific guidance.
For bulk printing, a practical workflow is to export item data containing call number and copy number, upload the spreadsheet here, map the call-number column to the label source and map the copy-number column when you want it shown. The tool does not connect directly to your Koha database, so you remain in control of which records are processed.
Koha also includes its own Quick Spine Label Creator. Koha documents that feature as a way to print a quick spine label and lets administrators define the fields through the SpineLabelFormat preference. VWS Online is most useful when you want browser-side batch preparation, spreadsheet mapping, custom paper geometry, partially used sheet positions or a workflow outside the Koha staff interface.
Dewey spine label formatting
Dewey call numbers are commonly displayed with the class number on one or more lines followed by a book number, author mark, year, copy designation or other local elements. There is no single physical label layout that every Dewey library must use. Label width, local shelving practice and the exact call-number string all influence where line breaks are placed.
The tool's Dewey mode uses a transparent printing heuristic. Shorter class numbers are kept together when possible. A longer class number can be divided around its decimal to fit a narrow label, and following tokens are placed on additional lines. For example, a supplied value such as 813.54 SMI can become:
813.54 SMI
This is a formatting aid, not a classification decision. If your institution has already established authoritative line breaks, select Preserve my line breaks instead of relying on an automatic split.
Library of Congress spine label formatting
Library of Congress call numbers are often more naturally divided into components because the class letters, class number, Cutter elements and date can occupy separate physical lines. The tool's Library of Congress mode uses a printing heuristic based on that recognizable structure. A value such as QA76.73.J38 2026 can be displayed as:
QA 76.73 .J38 2026
OCLC's Connexion label documentation describes comparable spine-label line behavior for Library of Congress and Dewey call numbers. It also documents the SP1 spine-label format as supporting up to nine lines of eight characters for call-number and stamp text. That is why this tool starts with an optional 8-character / 9-line guide. It is a useful narrow-label reference, not a universal rule. Review the official OCLC call-number label formatting guidance when you need to compare your local workflow with Connexion behavior.
Why classification correctness is separate from label formatting
A well-formatted label can still contain an incorrect call number. The generator cannot determine whether a title should be classed at a particular Dewey number, whether an LC Cutter has been shelflisted correctly or whether a local collection prefix follows your institution's policy. For Library of Congress work, the Library of Congress maintains the Classification schedules and Classification and Shelflisting Manual. See the official Library of Congress classification resources when classification assignment itself needs to be reviewed.
The safe model is simple: use authoritative cataloguing tools and local policy to decide the call number, then use this generator to make that approved call number fit your physical label stock.
Auto, Dewey, LC and Preserve formatting modes
Auto detects common patterns. A value beginning with one to three letters followed by a class number is treated as an LC-style value; a value beginning with a Dewey-like numeric class is treated as Dewey; other text is preserved as supplied. Auto mode is convenient for mixed processing queues but should still be reviewed before printing.
Dewey applies the Dewey line heuristic to every row. Library of Congress applies the LC heuristic to every row. Preserve my line breaks is the most conservative option when a cataloguer or source system already contains the exact physical line divisions required by your library.
Character-per-line and maximum-line guides
Narrow spine labels have limited horizontal and vertical space. The revised tool therefore includes a character-per-line guide and a maximum-lines guide. The default eight characters and nine lines are inspired by a common OCLC SP1-style narrow spine-label format, but you can change both values to match your own stock.
When a line is too long, choose whether to wrap it to the selected character guide or keep it unchanged and receive a warning. Automatic wrapping is useful for rough batch preparation, but it can create undesirable breaks in classification notation. The warning mode is better when preserving an exact call-number component is more important than fitting the nominal character count.
Top stamps, bottom stamps and copy numbers
Many libraries place a location, collection abbreviation or other processing stamp above or below the call number. Examples include REF, JUV, ARCH, MAIN or a local collection code. The generator supports a static top stamp and bottom stamp for the whole batch, plus optional spreadsheet columns when the stamp changes by item.
Copy number can also be placed on its own line. In a Koha-oriented spreadsheet, map the column containing 952$t or the equivalent item copy-number field. If your library does not print copy numbers on spines, simply turn that option off.
Import spine labels from CSV or Excel
Batch import is one of the biggest improvements over the old single-label tool. Upload CSV, TXT, XLSX or XLS files of up to the browser safety limit shown by the interface. For CSV and Excel files, the page reads the header row and lets you choose:
- the call-number column,
- the copy-number column,
- an optional top-stamp column,
- an optional bottom-stamp column, and
- an optional copies/quantity column.
Common names such as call_number, itemcallnumber, 952$o and copynumber are detected as suggestions, but you should always review the mapping. A spreadsheet column named "Class" might mean classification in one library and patron class in another, so the tool never treats automatic mapping as authority.
If your call-number data currently exists only in MARC records, the MARC to Excel Converter can first create a spreadsheet view, including one-row-per-952 Koha item output. You can then bring the relevant call-number and copy-number columns into this label workflow.
Printing on A4, Letter, Legal or custom label stock
Physical accuracy depends on more than text formatting. The tool lets you choose A4, US Letter, US Legal or custom paper dimensions, portrait or landscape orientation, number of columns, automatic or fixed rows, label width and label height, page margins and horizontal or vertical gaps.
Before rendering the sheet, the layout engine checks whether the requested geometry actually fits on the selected paper. If four 50 mm labels plus margins and gaps cannot fit across the page, the tool stops and asks you to correct the dimensions rather than producing an overflowing print layout.
Browser preview is still not a substitute for a physical test. Printer drivers may apply scaling, minimum non-printable margins or "fit to page" settings. For adhesive stock, print one test page on ordinary paper, place it behind the label sheet and check alignment against a light source before using expensive stock.
Start at an unused label position
Partially used label sheets are common in library processing rooms. Throwing away a page because the first few labels have been used is unnecessary. The Start printing at label position control leaves earlier cells on the first page blank and places the first new label in the selected position.
If the sheet is configured as four columns by eight rows, it has 32 positions. A start position of 7 skips the first six slots. The generator validates that the requested starting position is available for the current rows and columns, which prevents a value such as position 40 from silently producing an unexpected page.
Typography for narrow book spines
Readability is usually more important than decorative styling on a spine. The tool provides sans-serif, serif and monospace choices, adjustable point size, bold text, horizontal alignment, vertical alignment and line height. Centered bold text is a practical starting point for many collections, but a technical or archive collection may prefer left-aligned monospace labels.
A larger font is not automatically better. A 14-point call number on a narrow 20 mm label may overflow even when the character count appears reasonable. Use the page preview together with the line warnings and physical test print.
Per-record copies and replacement labels
The single-label mode includes a physical copies setting, while spreadsheet imports can map a copies or quantity column. This is useful when one item needs a replacement label and another title has three identically shelved copies requiring the same printed call-number text.
Repeated labels are therefore not automatically treated as errors. Unlike item barcodes, duplicate spine-label text can be completely legitimate because multiple copies may share the same call number. The exported report keeps the source call number and requested copies so staff can reconcile the print job with the processing list.
Download CSV, Excel or TXT output
After preparing the labels, you can print the page-sized preview or download the processed data. CSV and Excel output include the original call number, formatted label text, copy number, top and bottom stamps, requested copies, detected formatting mode, line count, maximum line length and a review flag. TXT output is useful for a simple human-readable record of the final label text.
These exports help when a processing team wants one person to prepare the batch and another person to approve it before printing. They are also useful during relabelling projects because the final physical line breaks can be kept with the project documentation.
Recommended workflow for Koha migration and relabelling
- Clean and validate item call numbers before label work. Use the MARC21 Validator when the source is MARC21 and review Koha item fields separately.
- If needed, use MARC to Excel to create item-row spreadsheet data.
- Map the item call-number column, normally corresponding to Koha MARC21
952$o. - Map copy number when your label policy includes
952$t. - Choose Preserve mode when approved physical line breaks already exist; otherwise test Dewey, LC or Auto on a small sample.
- Set the actual paper, label dimensions, margins and gaps.
- Print one test page and compare the labels with both the catalogue record and the physical stock.
- Only then print the full batch.
If you are building new MARC item data rather than relabelling existing material, the Excel to MARC Converter and MARC21 Record Builder cover a different part of that workflow.
Common book spine label mistakes
- Using the barcode as the call number. A circulation barcode and a shelf mark serve different purposes.
- Assuming an automatic line break is a cataloguing rule. Automatic formatting is a physical-layout heuristic.
- Inventing Cutter or author marks during printing. Use the approved call number from the catalogue or your classification workflow.
- Ignoring copy information. If your local policy prints copy number, map it explicitly rather than adding it by hand after printing.
- Printing a whole batch without a paper test. Browser and printer scaling can shift labels even when the digital geometry is correct.
- Reusing a partially used sheet from position 1. Set the actual first unused label position.
- Uploading an unrelated patron export. A label file should contain only the item fields required for the print job.
- Treating a label preview as classification validation. Review classification against the appropriate schedules and local rules.
Privacy and browser-side processing
The revised label workflow is designed to parse the entered text and selected CSV, TXT or spreadsheet files in your browser. It does not need patron names, borrower details or private circulation histories. Keep label source files minimal: call number, copy number and optional location or collection text are usually enough.
Because Excel export uses a browser library loaded for the tool, network access may still be required to obtain that library when it is not already cached, but the source label data does not need to be submitted to a conversion endpoint for normal processing.
Related library tools
Spine-label work often sits between cataloguing and physical processing. The Koha Barcode Generator creates new item barcode ranges, while the Library Barcode Sheet Generator prints existing barcode and QR values. The Library Accession Number Generator manages accession sequences, and the Koha Label Template Generator helps with Koha-oriented label template planning. For data migration, use the Koha Migration Readiness Checker before committing a large production batch.
Frequently asked questions about book spine labels
Can I create spine labels from Koha call numbers?
Yes. Koha MARC21 952$o stores the item call number and 952$t stores the copy number. Upload a CSV or Excel export, map those columns, review the formatted lines and print a test sheet.
Does the tool validate whether my Dewey or LC call number is correct?
No. It formats the call number you supply for a physical spine label. Classification assignment and shelflisting still require the appropriate schedules, local policy and cataloguing judgment.
How does Library of Congress call-number formatting work?
The LC mode uses a transparent printing heuristic that separates the alphabetic class, numeric class and subsequent Cutter or date tokens into label lines. Review the preview because local label practice can differ.
How does Dewey spine-label formatting work?
Dewey mode keeps shorter class numbers together and can split longer class numbers around the decimal in an OCLC-style printing heuristic, then places following book-number or copy data on additional lines.
Can I upload CSV or Excel for bulk spine labels?
Yes. The revised tool accepts CSV, TXT, XLSX and XLS files, lets you map call-number, copy-number, top-stamp, bottom-stamp and copies columns, and processes the batch in your browser.
Can I print on a partially used label sheet?
Yes. Set the starting label position so the first page leaves earlier positions blank. The selected position must fit the configured rows and columns.
What does the 8-character and 9-line option mean?
It is a useful narrow-label guide inspired by OCLC SP1-style spine labels, not a universal library standard. You can change the character and line limits to match your label stock and local practice.
Are my call-number files uploaded to VWS Online?
The batch parsing, formatting, sheet layout and export workflow is designed to run in your browser. Avoid placing confidential patron or unrelated sensitive data in a label source file.
Continue the workflow
- 1Book Spine Label GeneratorComplete and review this result first.
- 2MARC21 Record Builderbuild a structured MARC21 bibliographic record and export it in librarian-friendly formats
- 3Excel to MARC Converter for Koha Librariesconvert spreadsheet cataloguing data into MARC21 records for Koha and other MARC-based systems
- 4MARC21 Validatorvalidate MARC21 record structure, fields, indicators, subfields and optional Koha 952 item data before import or migration
