ATTDISP Command In AutoCAD : Controls The Visibility Overrides For All Block Attributes In A Drawing

AutoCAD’s ATTDISP command controls the global display of Block attributes in a drawing. This guide explains what it does, how to use it step‑by‑step, why it may not behave as expected, alternatives and fixes, practical examples, and a helpful FAQ.

Table of Contents

What is the attdisp command?

The attdisp command in AutoCAD is a tool that controls visibility overrides for all block attributes in a drawing. It toggles how attributes are displayed for block references — for example, whether attributes follow their definition visibility, are hidden on screen, or are forced to display even if flagged invisible in the block definition.

Key ideas:

Attributes are text entities attached to block definitions used to store metadata (tags/values).
attdisp applies a global display mode to attribute display, affecting all block references in the current drawing.

How attdisp works (explanation)

When you run attdisp, AutoCAD presents modes that determine how attributes appear on screen. The most common modes are:

Normal — Attributes display according to their block definition flags (the default behavior).
Hide — Attributes are hidden (not displayed) for all block references in the drawing.
Show — Attributes are displayed on screen even if the attribute in the block definition is set as invisible.

Using attdisp does not change the attribute data itself — it only changes visibility on screen (and in some cases in plotting, depending on settings). To change attribute definitions permanently you must edit the block definition.

How to use attdisp — step by step

At the command line type: ATTDISP (or _ATTDISP for keyboard command compatibility).
Press Enter. AutoCAD will prompt you with the display mode options (for example: Normal/Hide/Show).
Enter the option you want (type the word or use the displayed shortcut letter) and press Enter.
Inspect your drawing: the attribute visibility will update immediately for all block references.

Shortcut and quick tips:

Using the underscore prefix (_ATTDISP) ensures compatibility between localized versions of AutoCAD.
If you prefer the keyboard-only method, type the exact option name shown by AutoCAD (for example, Hide) and press Enter.

Practical examples (before/after scenarios)

Example — Preparing a clean plot: Set ATTDISP = Hide before plotting architectural layers that include many attribute values you do not want on the printed sheet.
Example — Verifying invisible attributes: If some attributes are not visible but you need to inspect them, set ATTDISP = Show to force display of attributes even if they were defined as invisible.
Example — Normal editing: Use ATTDISP = Normal when you want to view attributes according to their block definitions (typical design mode).

Why attdisp sometimes doesn’t work (common causes and fixes)

If running attdisp appears to have no effect, check the following possibilities:

Attributes on a turned-off or frozen layer: If the layer containing attribute text is off, frozen, or locked, attributes won’t display. Fix: turn the layer on/thaw/unlock it.
Block has been exploded: Exploded block references become separate entities; attribute behavior changes. Fix: reinsert or redefine the block properly.
Attribute text height = 0 or extremely small: Attributes might be present but not visible due to scale/height. Fix: edit the block or attribute definition to set appropriate text height.
annotation scale or viewport scale issues: If attributes are annotative or controlled by viewport scale, they may not show at certain scales. Fix: check annotation settings and scales.
Attributes are truly deleted or not defined: If attribute definitions were removed from the block definition, attdisp cannot show what doesn’t exist. Fix: use BATTMAN or BEDIT to re-add definitions.
Drawing corruption: If the drawing is corrupt, behavior can be unpredictable. Fix: run AUDIT or open the drawing with RECOVER.
You changed display mode but blocks were not updated: After editing a block definition, references may need to be synchronized. Fix: run ATTSYNC to update block references with new definitions.
Attribute flagged as constant: Constant attributes may not behave as editable attributes. Fix: edit the attribute definition inside block editor if needed.

Alternative commands and related tools

BATTMAN (Block attribute manager): Manage attributes inside block definitions — set visibility, reorder, edit tags and prompts.
ATTSYNC: Synchronize block references after you change attribute definitions. Always run this after editing definitions when you need existing references updated.
ATTEDIT / EATTEDIT: Edit attribute values on block references (single or batch edits; EATTEDIT provides a more advanced dialog).
BEDIT / REFEDIT: Edit the block definition directly to change attribute properties (visibility flags, Text style, height).
AUDIT / RECOVER: Repair drawing problems that may be preventing attribute display.
Properties palette: Select a block reference to inspect attribute properties; some changes can be made at the reference level depending on attribute flags.
ATTDIA (system variable): Controls whether attribute editing uses a dialog box or command-line prompts. Set to 1 for dialogs, 0 for command-line.

Tips and best practices

Use BATTMAN for bulk edits to block attribute definitions rather than editing many individual references.
After changing attribute definitions in a block, always run ATTSYNC to ensure all references get updated.
When preparing drawings for plotting, switch to Hide to remove attribute clutter temporarily — but remember to set back to Normal when needed.
Keep attribute text layers consistent across blocks to help control visibility with layer tools.
Use descriptive attribute tags and apply consistent text styles and sizes to avoid invisible or mis-scaled attributes.
If collaborating, document any block changes so others know to run ATTSYNC after opening the drawing.

FAQ

What’s the difference between “Hide” and making an attribute invisible in the block definition?

Hide (via attdisp) is a global display override that hides attributes on screen for all block references. Making an attribute invisible in the block definition flags that attribute to be hidden by default for that block — but attdisp Show can force those invisible attributes to display. Use block edits to permanently change default visibility.

How do I show attributes that are invisible on a specific block only?

Edit the block definition with BEDIT or BATTMAN and change the attribute’s visibility flag (uncheck Invisible). Then run ATTSYNC if there are existing references. Do not rely on attdisp, because it applies to all blocks globally.

Why don’t my changes to attribute definitions appear in existing block references?

After you modify attribute definitions in the block, run ATTSYNC to update existing block references. Without synchronization, references keep old attribute definitions.

Can I hide attributes only for a few blocks instead of the whole drawing?

Yes. Instead of attdisp, edit the block definition to set attributes as invisible or move attribute text to a layer you can turn off for those selected blocks. Alternatively, create a separate block version with different attribute visibility and use that block where you want hidden attributes.

Do invisible attributes still print?

Invisible attributes may still print depending on your settings and whether you forced display with attdisp Show. If the attribute entity is hidden because of layer settings or the attribute flag, it generally won’t print. Always check a print preview.

What should I do if attdisp doesn’t change anything at all?

Check layer visibility, annotation scale, attribute text heights, and whether the block references were exploded. Run AUDIT and RECOVER if the drawing seems corrupt. If you edited block definitions, run ATTSYNC. Also verify that you used the correct ATTDISP option.

How do I edit attribute values for many blocks at once?

Use EATTEDIT (Enhanced Attribute Editor) to edit attribute values in batches. BATTMAN also helps manage definitions; for scripted changes consider using a LISP routine or data extraction if you need large-scale automation.