EF-Tools ✓

EF-Tools is a free, open-source (GPL-3.0) pyRevit extension containing more than 50 tools for common Revit tasks, created by Erik Frits, an instructor at LearnRevitAPI.com who built the collection specifically to help fellow Revit users "solve boring tasks with a click." Unlike a standalone Revit add-in, EF-Tools installs directly through pyRevit's own Extensions menu -- it's built as an extension of pyRevit's platform rather than a separate, independently-installed plugin.

That distribution model matters practically: a firm or individual already running pyRevit (itself free and covered elsewhere in this catalog) can add EF-Tools' entire 50+ tool library in a few clicks through pyRevit's Extensions menu, without a separate download, installer, or license process of its own. For firms already invested in the pyRevit ecosystem, this is closer to installing an app from an app store than adopting a new standalone piece of software.

As a genuinely free, GPL-3.0 open-source project, EF-Tools carries no licensing cost at all, and its GPL-3.0 license specifically means the source code itself is open for inspection or modification by anyone technically inclined to do so -- a meaningfully different commitment to openness than a merely "free to download" closed-source tool.

The creator's background is worth noting specifically: Erik Frits runs LearnRevitAPI.com, an education-focused site teaching Revit API development, and EF-Tools functions partly as a practical showcase of pyRevit-based tool development alongside being genuinely useful on its own -- support is available directly via email through that same educational platform, which is a somewhat unusual but genuine support channel for a free open-source tool.

Editor’s takeBIM•STACK editor's take: EF-Tools is a strong, no-cost addition for any team already running pyRevit, precisely because the installation friction is nearly zero -- it's an Extensions-menu click away rather than a separate evaluation and procurement decision. The honest scope limitation is that it's entirely dependent on pyRevit already being installed and set up, so firms not yet using pyRevit should evaluate that platform first; EF-Tools isn't a standalone alternative to it.

Because EF-Tools' individual tools each solve one specific, well-defined Revit task, most users can start using any given tool within the collection immediately once installed -- there's no new interface paradigm to learn beyond what pyRevit itself already introduces, since EF-Tools' tools appear in the Revit ribbon just like pyRevit's own built-in tools.

The primary prerequisite is being comfortable with pyRevit itself first -- since EF-Tools installs and runs entirely within that platform, a team's actual ramp-up time depends more on their existing pyRevit familiarity than on anything specific to EF-Tools' own tools.