Overview
Layers and Tags are two complementary ways to organize, find, and control items in a design, document, or data environment.
Layers control where objects sit and how they behave in the visual/structural stack (visibility, stacking order, grouping and edit/lock state).
Tags are metadata labels you attach to objects to classify, and drive workflows (semantic grouping, properties, etc).
This FAQ explains the conceptual difference, practical use cases, and best practices.
Quick comparison
Aspect | Layers | Tags |
Primary purpose | Visual/structural organization (stacking, grouping, visibility, locks) | Semantic/categorical organization (labels, search, filters, automation) |
Relationship to objects | Usually exclusive per stack or hierarchical (one object in one place in the layer stack; can be grouped) | Non-exclusive — an object can have multiple tags |
Typical operations | Move up/down, show/hide, lock/unlock, group/ungroup, rename | Add/remove label, filter/search by tag, bulk-apply rules, automation triggers |
Best for | Managing rendering order, visibility per view, and edit control | Finding, filtering, filtering by property, workflow rules, metadata-driven exports |
Visibility across views/pages | Often global within a document or per-page layers | Available across all views/pages where the item exists (tags travel with items) |
Use in automation/APIs | Used to determine stacking/visibility in exported output | Used for filtering, selection, batch operations, triggers |
When to use Layers:
You need to control what is visible in a view or export (e.g., hide construction lines).
You must control draw/stack order (which object appears on top).
You want to lock elements to prevent accidental editing.
You want to create named structural groups (backgrounds, annotations, UI chrome).
Example: Put all dimension lines in a “Dimensions” layer so you can hide them during a presentation.
When to use Tags:
You want to classify objects by semantic meaning (e.g., “Phase/Building”, “Reviewed”, “Client A”).
You want to find and filter objects across multiple pages or projects.
You want to apply workflows or rules (e.g., all “For Approval” items appear in a review board).
You want to let objects belong to multiple categories simultaneously.
Example: Tag elements with “For Revision” and “Structural” so the structural team can quickly isolate items requiring revision.
Practical workflows and examples
Example: Preparing drawings for client review
Use Layers to separate:
Base geometry
Annotations
Revision clouds
Dimensions
Toggle visibility or lock layers to create a clean review view.
Use Tags to mark statuses:
“Ready for Client”
“Internal Review”
“Urgent”
Filter by tags to pull all items ready for client review into the area dashboard or export model.
Example: Team responsibilities
Place shared geometry on a “Core” layer so team members don’t accidentally move it (lock layer).
Tag items with Building (“Residential”, “Commercial”, “Retail”) so each team can focus on their respective tag when designing.
Best practices
Layers
Keep layer names short and descriptive (e.g., “Dimensions”, “Annotations”, “Ref—Site Plan”).
Use layers for visual/structural separation only. Don’t overload a layer to attempt semantic classification.
Lock layers that should not be edited.
Use view presets that combine layer visibility states for different audiences (presentation vs construction).
Tags
Use a consistent taxonomy (naming convention) and document it. Example: prefix status tags with
status:(e.g.,status: for-review).Limit tag proliferation; retire or merge redundant tags.
Allow multiple tags per object for cross-cutting concerns (status, discipline, client, priority).
Both
Use both: layers for how things look and behave; tags for what things are.
Consider creating templates that include both a layer structure and a standard tag set for new projects.
Common questions
1. Can an object belong to both a Layer and one or more Tags?
Yes. Layers and tags serve different roles and are complementary. An object typically resides on a layer (for stacking/visibility/lock) and can have any number of tags for classification, searching and automation.
2. Are layers exclusive? Can an object be on multiple layers?
In most systems, an object has a single location in the layer stack (so layers are mutually exclusive in terms of placement). If you need an object to be visible in multiple contexts, use tags or duplicate the object onto different layers.
3. Can tags affect visibility the same way layers do?
Tags themselves are metadata and do not inherently change draw order or lock state.
4. Which should I use for versioning and approval workflows?
Use Layers. Layers are ideal for approvals, statuses (e.g., Draft, For Review, Approved). You can save views by keeping the right layer visible and create presentation views from these.
5. Which is better for exporting subsets (e.g., export only annotations)?
Either can work:
If export depends on visual arrangement or locking/visibility per view, use layers.
If export depends on semantic classification (e.g., export only items tagged “Site Plan”), use tags or a combination (tag + layer-based view). Many workflows rely on both: use layers to define visual groups and tags to mark semantic subsets for export.
6. If I want to hide all non-architectural content for presentation, should I use layers or tags?
Layers are best for presentation visibility; ensure architectural items are on visible layers and hide other layers. Tags can help create a saved filter but layers control presentation order and locking.
7. Why can’t I lock items by tag?
Tags are metadata; locking is usually a layer/object-level property. If you need to lock many items at once, bulk-select by tag and then lock the selected objects or move them to a locked layer.
Final tips
Educate your team on the difference—document the conventions and include examples.
Keep layer usage minimal and clear; use tags for richer classification.
Combine them: use layers for presentation and tags for metadata association.