Vectorworks http://www.vectorworks.net provides an open architecture that allows developers to supplement or replace existing Vectorworks functionality. From the user’s perspective, these new tools, menu commands, and objects are indistinguishable from those built into Vectorworks. As such, they are first-class solutions for the user.
The SDK https://www.vectorworks.net/en-US/support/custom/sdk/sdkdown provides OS-independent functionality for accessing the application routines. Also, it provides functions for creating OS-independent User Interfaces for your plug-ins.
The Vectorworks SDK uses the C++ language to develop extension functionality. To develop SDK plug-ins for Vectorworks, you will need the following tools:
Before you begin, you should review the Vectorworks environment.
The Vectorworks SDK provides some specific types. A developer should use the recommended types. Here is a short list of the most commonly used types:
Vectorworks plug-in is a dynamic library on Windows and a specific type of bundle on Mac.
On launch, Vectorworks enumerates the 'Plug-ins' folder next to the application for dynamic libraries (or bundles). Also, Vectorworks traverses shortcuts (aliases) placed in the folder hierarchy.
Each Plug-in module is a VCOM (Vectorworks Component Object Model) provider library. This library provides one or many VCOM implementations of standard interfaces for the different extensions.
More information on the topic see here.
VectorWorks Foundation Classes
Vectorworks 2026 introduces the requirement for script plugins that are encrypted/obfuscated and SDK plugins to have a satellite credentials file that defines who is the developer of the plugins is.
More information can be found here: Plugin Credentials