Crop Region Sync
PremiumCopy crop region settings from active view to selected target views. · Explore the live interface below - every control works exactly as it does inside Revit®.
Architecture
Structure
Steel
Precast
Systems
Insert
Annotate
Analyze
Massing & Site
Collaborate
View
Manage
Add-Ins
NexionTools
Select
Highlight
Rooms
Parameters
Sheets & Views
Data
Manage
QC
Test it Live - exactly as if you are in Revit
Loading interactive demo…
Get Started in Minutes
Four simple steps to bring Crop Region Sync directly into your Revit® environment.
1
Create Account
Sign up for a free NexionTools account - no credit card required.
2
Download Installer
One installer, 52 professional Revit® tools. Under 15 MB.
3
Open Revit
Crop Region Sync appears in your ribbon automatically - ready to use.
4
Activate License
Enter your Premium key to unlock full features.
Ecosystem · Sheets & Views
Try NexionTools completely free.
Get full access to all 40 premium Revit® plugins. No credit card required.
Why Crop Region Sync exists
Two plans of the same floor should crop identically. They rarely do. One was set up before the building grew, another was adjusted for a presentation, and now the sheets show slightly different extents of the same level - which nobody notices until they are side by side on a printed set.
How Crop Region Sync works
Pick a source view - the one that is already cropped correctly. Its crop size in millimetres, whether the crop is active, and whether it is visible are shown as pills, and a red one tells you when the source has no readable crop at all.
Pick the target views. The list carries type, level and search filters, All, None, Invert and Same Type helpers, and a running count of how many are selected.
A confirmation names the source, counts the targets, and states plainly that the crop region, the crop visibility and the annotation crop will be overwritten.
The crop box, its transform, the active and visible flags, and the annotation crop state are copied across in a single transaction.
Targets that accept the crop end up identical to the source. Any that refuse - a view owned by another user on a workshared model is the usual reason - are counted and reported rather than quietly left behind.
Before
Crop regions are matched by eye and by dragging handles, which is approximate and does not survive the next change.
After
One view is the reference and the rest are copied from it, so matching extents is a deliberate action rather than a coincidence.
When to reach for it
- Making every plan of a level crop to the same extents before a sheet set is issued.
- Propagating a crop change after the building footprint grows.
- Setting up a new set of views to match an existing, approved one.
What it does not do
- It copies the crop from one view to others. It does not create views or place them on sheets.
- Views of genuinely different types or orientations can accept a crop that does not make sense for them - the source is your responsibility.
- Template views are excluded from both lists, and so are sheets, schedules and legends - none of them have a crop region to copy.
- On a workshared model it does not check views out first. A view owned by someone else simply fails inside the run and is counted, without an ownership message to explain why.
Questions
- How do I make several Revit views crop the same way?
- Revit has no "match crop" command. This copies the crop box, its transform, and the active, visible and annotation-crop states from one view onto as many others as you select.
- Does it copy the annotation crop too?
- Yes - the annotation crop state travels with the rest, which is usually the part that gets forgotten when matching crops by hand. On view types where that setting is read-only it is skipped without comment.
- Can I undo it?
- Yes, the whole operation runs as a single transaction.