Plot Styles — Use plot styles (CTB/STB) to control output appearance (intro)

Historical Context & Motivation

Before the era of digital CAD, engineers and drafters produced drawings with ink on vellum or mylar, carefully selecting pen weights, ink colors, and line types to convey information hierarchy on the printed page. When AutoCAD arrived in 1982, it digitized the drawing process but initially offered limited control over how on-screen colors mapped to physical pen plotters. Early pen plotters had carousels holding pens of different widths, and AutoCAD simply mapped object colors to pen numbers — a crude but effective scheme. As the software matured and electrostatic and inkjet plotters replaced pen-based hardware, Autodesk recognized that separating visual appearance from geometric data was essential for professional output workflows.

The central question that plot styles answer is fundamentally one of abstraction: how do you maintain a single source drawing while supporting multiple output appearances — monochrome construction documents, color presentations, and screened background sheets — without duplicating geometry? This is the same separation of concerns principle familiar from software engineering, where data logic is isolated from presentation.

Core Principles & Definitions

A plot style is a collection of property overrides that modify how an object is rendered at plot time without changing its properties in the drawing database. These overrides are organized into plot style tables — files with either a .ctb or .stb extension — that are attached to layouts and referenced during the plot pipeline. Understanding the distinction between these two table types, and when to use each, is foundational to mastering AutoCAD output.

Visual Explanation — The Plot Style Pipeline

The diagram above illustrates the fundamental pipeline. On the left, the drawing contains objects assigned to various AutoCAD Color Index (ACI) colors — red for walls, yellow for dimensions, green for hatching, and so on. These colors are chosen for on-screen legibility against a dark model-space background. In the middle, the CTB table acts as a lookup function: each color index (1 through 255) maps to a set of output properties. On the right, the final printed sheet renders all objects in black with varying lineweights and screening percentages, producing a professional, hierarchical document. The critical observation for computer science students is that this pipeline implements a classic decorator pattern — the plot style table wraps the drawing data with presentation logic without modifying the underlying objects.

How Plot Styles Work — The Rendering Pipeline

When you issue a PLOT command (or Ctrl+P), AutoCAD traverses every visible object in the designated plot area and evaluates it through the plot style table. The resolution order depends on whether the drawing uses CTB or STB mode, and understanding this resolution is essential to debugging unexpected output.

CTB Resolution Logic

In a CTB drawing, the resolution is deterministic and simple. AutoCAD reads the object's effective ACI color (which may be inherited from its layer via ByLayer or set explicitly via ByObject). It uses this color index as a key to look up the corresponding entry in the attached .ctb file. The entry's properties — output color, lineweight, screening, line-end style, line-join style, and fill style — override the object's native properties for the duration of the plot. This can be expressed as a function:

STB Resolution Logic

In an STB drawing, the resolution involves an extra level of indirection. Each object (or its layer) carries a plot style name property — a string like "Heavy Walls" or "Light Annotation". AutoCAD looks up this name in the attached .stb file's dictionary of named styles. If the name is not found, the object plots with its native properties. This is analogous to CSS class-based styling where a missing class simply results in default rendering.

Detailed Breakdown — CTB vs. STB

Choosing between CTB and STB mode is one of the first architectural decisions in an AutoCAD project, much like choosing between a relational and document database shapes your entire data access layer. Both systems achieve the same end goal — controlling output appearance — but they impose fundamentally different constraints on your drawing organization. The following diagram and table provide a side-by-side comparison to help you reason about which approach fits a given workflow.

Worked Example — Creating and Applying a Monochrome CTB

The most common plot style task is creating a monochrome CTB that converts all colors to black while differentiating objects by lineweight. Let us walk through this process from start to finish using the monochrome.ctb as a base template.

Strengths, Limitations, and Trade-offs

Connection to Advanced Plotting Concepts

Plot styles are one component of a broader output ecosystem in AutoCAD. As your projects grow in complexity — from single-sheet exercises to multi-discipline construction document sets — you will encounter several advanced topics that build directly on the foundations covered here. Understanding where plot styles sit in this larger landscape helps you plan your learning path and avoid architectural mistakes that are costly to refactor later.

For computer science students, the programmatic angle is particularly relevant. AutoCAD exposes its plot style infrastructure through the .NET API and ObjectARX (C++ SDK), enabling you to write plugins that dynamically generate or modify plot style tables. Imagine a CI/CD pipeline for construction documents where a commit to a CAD file repository triggers automated plot style validation, generates PDF outputs with standardized lineweights, and flags non-compliant color assignments — this is the kind of infrastructure that firms increasingly build using AutoCAD's API layer.

Practice Problems

Lesson Summary