Drop a Python file into a folder and it becomes a button on the Revit ribbon — then drag and drop to arrange tabs, panels and groups right in the window, and apply without restarting Revit.
Every team that writes Revit scripts hits the same three problems: getting scripts onto the ribbon where colleagues can click them, rearranging where the buttons sit as the script count grows, and knowing who ran what. The most common platform today ties ribbon layout to the folder structure on disk, so every presentation change becomes a rename or a file move.
Ribbon layout is locked to folder names, so moving a button means renaming or relocating the whole script folder, then reloading. Whoever maintains the library has to memorise a naming convention instead of seeing the layout.
Quitting Revit with a large project open just to see a button you added costs ten minutes every time you try something.
A Python script running in the Revit process can modify the model, read and write files, and reach the network. If the tool never asks before running unfamiliar code, IT has grounds to block the whole platform.
Script Hub only provides the platform — running scripts and managing where they sit on the ribbon — so the script library stays yours, wherever you keep it and however you write it.
The interface is matched to the tool window running in Revit.
Project CleanerPurge dead views, empty groups, unused families and leftover CAD imports — shrink the file before you issue.
Style ForgeAudit usage and duplicates; safely create, edit, duplicate, merge and delete Object, Line, Text, Dimension, Viewport and Scope Box styles. The AI assistant and account-saved presets only queue changes — you press Apply yourself.
Batch ExporterExport PDF, DWG, IFC and NWC from a saved sheet set, named to the project rule with a per-issue log.
