Revit Change Revision Cloud Color: Step-by-Step Guide
Key takeaways
- Set revision cloud color project-wide in Manage > Object Styles > Annotation Objects > Revision Cloud so every resubmittal plots the same.
- If a cloud plots the wrong color, trace overrides top-down: object styles, then phase filters, then view templates and element-level graphic overrides.
- Arc radius is a type property; use a 1/2-inch radius at 1/8-inch scale and bump to 5/8-inch at 3/32-inch so bubbles stay legible after scanning.
- Set revision cloud line weight to 3 and export PDFs as vector, since grayscale plots and raster export can make clouds vanish on plan-check copies.
- Create the revision in Sheet Issues/Revisions before sketching clouds, and enforce your office standard with a view template like PERMIT-CD.
To change a revision cloud's color in Revit, go to Manage > Object Styles > Annotation Objects > Revision Cloud and edit the line color there. That setting controls what plots on your D-size resubmittal sheets, so getting it right before the city sees your correction letter response matters.
How do you change revision cloud color in Revit?
Select the cloud, and you can change its color two ways. For a one-off fix, pick the cloud, open Properties, click Edit Type, and adjust the line color in the type properties. That only affects clouds of that type in that project.
For a project-wide change, go to Visibility/Graphics (VV), find the Annotation Categories tab, and override the Revision Clouds line color there. This catches every cloud in every view, including ones placed by a contract drafter who never touched your type settings. Autodesk's Revit Help covers revision cloud type properties and visibility overrides if you want the full parameter list.
Object style override vs per-cloud override
There is a third layer: Manage > Object Styles, under Annotation Objects. Setting Revision Clouds there changes the default for the whole project template, not just the current view. Per-cloud overrides win over object styles, so a cloud that prints wrong usually has a manual override hiding somewhere.
Why object styles are the right place for an office standard
If you draft 1-3 permit sets a month, you want the color decided once, in your template, not re-decided per sheet. Setting the Revision Clouds object style in your office template means every resubmittal plots the same, and a city correction letter never comes back because a cloud plotted too light to scan. Your template carries the standard; the resubmittal workflow just has to follow it.
Where does the cloud color come from: object styles, revisions, or phases?
Revit assigns revision cloud color from the Revision Clouds line under Manage > Object Styles. If a cloud plots red when your standard says black, something is overriding that object style. The usual suspects are phase settings and view-specific graphic overrides, not the revision schedule.
Checking phase filters and graphic display options
Open the view's Properties and check Phasing first. If the sheet view or the model views feeding it have a phase filter that applies override graphics, clouds on demolished or existing work can inherit a phase color. Then open Graphic Display Options and look at Phase Fill and line overrides. Turn on Thin Lines temporarily and select the cloud to confirm which category it actually belongs to.
The fastest way to trace the winning control is to work top-down: object styles set the baseline, then phase filters, then view overrides, then any element-level graphic display override you or your contract drafter applied by right-clicking. Each level replaces the one above it for that view only. If the cloud looks right in one view and wrong on the sheet, the fix lives at the view or template level, not in Object Styles.
View templates that fight your cloud color
A view template with V/G Overrides can lock the cloud color per view, and it will beat your object standard every time. On resubmittal sets where sheets come from multiple template sources, this is why one D-size sheet plots with black clouds and the next plots blue. Set the cloud color once in your template, then check https://studio.pretiva.io/residential-designers for how a repeatable sheet setup keeps this from drifting between permit sets.
How do you change revision cloud size in Revit?
Cloud size is a type property, not a per-instance setting, so you fix it once and every cloud on the sheet matches.
Arc radius in type properties
Select any revision cloud, click Edit Type, and adjust the Arc Radius value. That number controls the size of each bubble in the cloud. A 1/2-inch radius reads fine on a detail, but it disappears when the sheet scales down. Duplicate the type and create a Small (1/4") and Standard (1/2") version so your office standard covers both. The Autodesk Help documentation for the Sheet Issues/Revisions dialog covers how revision and cloud settings propagate across the project (Autodesk Help).
Sizing clouds for D-size sheets
On a D-size resubmittal plotted at 1/8-inch, a 1/2-inch arc radius stays legible after the city scans your PDF. At 3/32-inch, bump the radius to 5/8-inch or the bubbles merge into a blob. Pair the radius with the revision cloud line weight in Additional Settings so the outline survives plan check. The same sizing logic applies to clouds Pretiva Studio places overnight (Pretiva for interior designers).
How do line weights control how clouds print on a permit resubmittal?
A revision cloud drawn at line weight 1 can look fine on screen and vanish on a scanned resubmittal. City plan-check staff work from PDFs printed or scanned at 300 dpi or less, and a hairline cloud around a correction is easy to miss. Set the cloud's line weight so it plots heavier than the annotation around it.
Line weight by object style vs thin lines mode
Revision cloud appearance is controlled in Manage > Object Styles > Annotation Objects > Revision Cloud. Set Line Weight to 3 for printed permit sets; leave "Thin Lines" off when checking plot output, since it overrides everything to hairlines on screen. The line pattern stays solid; dashed clouds confuse reviewers about what changed.
| Setting | Where | Suggested value |
|---|---|---|
| Line Weight | Object Styles > Revision Cloud | 3 |
| Line Color | Object Styles > Revision Cloud | Black (plots true) |
| Line Pattern | Object Styles > Revision Cloud | Solid |
Testing plotted output before you submit
Print one D-size sheet to PDF at your resubmittal settings, then print that PDF to paper or view it at 100% zoom. If the cloud reads lighter than your dimension strings, bump the weight to 4. Tools like Pretiva Studio place clouds inside your own Revit template, so they inherit whatever your office standard sets (https://studio.pretiva.io/ai-drafting-revit).
How do you add a revision cloud and tag it correctly?
Sketching the cloud is the easy part. On the Annotate tab, pick Revision Cloud, draw it around the changed geometry, and Revit snaps the cloud to the revision number and sequence you have set. The mistake that costs hours at plan check is drawing clouds before the revision exists in the project, which forces you to reassign every cloud later.
Assigning clouds to numbered revisions
Open the Sheet Issues/Revisions dialog (Manage tab on newer releases) and add the revision first: sequence number, description, date, and whether it is issued by cloud or by tag. Then, when you draw the cloud, pick that revision in the options bar. If the city's correction letter lists three items, create three revisions so the resubmittal tells the reviewer exactly what changed. The cloud's color and line weight follow the revision settings, not the sketch, so get this order right before you draw anything. Autodesk's documentation on revision clouds and their plot behavior covers how issued revisions affect visibility on printed sheets.
Revision schedules on the title block
A revision schedule placed on the title block family pulls every revision assigned to that sheet automatically. Add one to your D-size title block once, and each resubmittal populates the revision table without manual typing. Pair it with a revision tag on the cloud itself so the cloud number matches the schedule row. If your contract drafter starts from a scan or as-built set, tools like Pretiva Studio's scan-to-as-built workflow hand you a model that already carries your revision setup, so clouds land on the right revision from the first sketch.
What should your office standard for clouds look like?
A written standard is what lets a contract drafter, a new hire, or an AI add-in produce clouds you don't have to fix sheet by sheet. It removes the guesswork from every resubmittal.
A sample standard for residential permit sets
Pick one setting per item and write it down:
- Color: one color, never by phase. Red (RGB 255,0,0) plots predictably on a grayscale D-size sheet and survives city scanning.
- Arc radius: 1/16" for residential plans and details. Larger radii swallow small corrections at 1/4" scale.
- Line weight: pen weight 2 (0.18mm). Heavy enough to read, light enough not to fight the linework it surrounds.
- Tag: revision number only, no date, no description on the cloud. The revision schedule carries that.
- Revisions: numbered per issue, one numbered revision per resubmittal, so the correction letter maps to your clouds.
Enforcing the standard with a view template
Put the object style overrides into a view template named PERMIT-CD and apply it to every sheet-bearing view. Then the standard is not a habit, it is the template. Any drafter or AI output opened in a view with that template inherits your color, radius, and line weight without anyone remembering the rules.
How do cloud settings interact with PDF export and city scanning?
A cloud that looks right on your monitor can disappear on a plan-check copy. Three settings cause it: color output, vector vs raster export, and line weight.
Grayscale plot settings
If your page setup plots in grayscale, a red cloud and a black cloud both arrive at the printer as mid-gray. On a scanned resubmittal, gray often drops out entirely. Either plot in color so the cloud survives, or keep clouds black and rely on the revision tag and delta number to carry the information. Check the plot style table (CTB) assigned to your D-size sheet setup, not just the on-screen color.
Raster pitfalls on resubmittal
Exporting PDFs as raster instead of vector turns crisp cloud arcs into fuzzy edges that scan badly and can blur into the linework they surround. Autodesk documents the vector vs raster choice in its PDF export settings for Revit. Vector output keeps arcs sharp at any scan resolution; use raster only for views with heavy raster-based fills. Then zoom to 400% on one cloud in the finished PDF before you send the set.
Can AI drafting tools place clouds to your standard?
Overnight drafting only saves time if the clouds come back already matching your office standard, so the review step is a checklist, not a redraw.
Checking AI-placed clouds against your standard
Open Object Styles first. Confirm the returned sheets placed every cloud on your revision subcategory, not on a generic detail line, so your line weight and color settings still govern them.
Then check the revision schedule. Each cloud should reference a numbered revision with the right date and description, so the city sees a clean sequence on the resubmittal.
Spot-check tag placement and cloud size on one sheet per level. If a cloud reads too small when plotted on D-size, fix the arc setting once in your template, not sheet by sheet.
Anything wrong gets redlined back for the next run. Your stamp goes on only after the schedule, the subcategory, and the plotted line weight all check out.
FAQ
Why is my revision cloud not printing in color on my permit set?
A grayscale plot setup is the usual cause. Check the plot style table (CTB) assigned to your sheet setup; it converts red and black clouds to the same mid-gray, which can drop out on a scanned copy. Either plot in color or keep clouds black and rely on the revision tag and delta number to carry the information.
What is the default revision cloud arc radius in Revit and should I change it?
The arc radius is a type property, and the shipped default is larger than most residential work needs. For permit sets, duplicate the type and create a Small (1/4") and Standard (1/2") version. At 3/32-inch plot scale, bump the radius to 5/8-inch or the bubbles merge into a blob after the city scans your PDF.
Can I make revision clouds thicker only on certain sheets?
Not per sheet directly. Line weight is set in Object Styles, so it applies project-wide. The workaround is a view template with a V/G override for the Revision Clouds category, applied only to the sheet-bearing views that need a heavier weight. That beats the object standard for those views, so use it deliberately and document it.
How do I delete a revision number after deleting a cloud?
Deleting a cloud does not delete its revision. Open the Sheet Issues/Revisions dialog and remove the revision there. Revit blocks deletion if clouds still reference that revision, so confirm no clouds remain assigned to it first. On resubmittals, keep one numbered revision per issue so the correction letter maps cleanly to your clouds.
Do revision clouds show up in 3D views or only on sheets?
Revision clouds are annotation elements, so they live in views, not on sheets themselves. They appear in plan, section, and elevation views where the assigned revision is set to visible, and those views plot onto your sheets. They do not exist in 3D views. If a cloud is missing on a sheet, check the view it was sketched in.