Skip to main content

Features

Compile your VBA to a native DLL, license what you build, and ship it. Every capability below is shown as it appears in VBA Padlock Studio.

Compiled, not hidden

VBA Padlock does not obfuscate your source or hide it behind a password. It compiles your procedures to bytecode inside a native DLL and removes them from the file you ship. What ships is a document that calls into a DLL, not a document with your code in it.

  • Automatic analysis of your existing Office file, procedure by procedure
  • 32-bit and 64-bit DLLs generated together, so one build covers both Office architectures
  • Original source removed from the Office file, not hidden inside it
  • Wrappers and the VBAPLBridge module generated and injected for you
  • Classes, Property accessors, Enum, Type, and 80+ built-in functions supported

How compilation works

The VBA Padlock Studio code editor showing a VBA module before compilation

What stays in your document

Not every procedure can move. Office has to be able to call some code in the file itself, and VBA Padlock tells you exactly which, before you ship. The Protection Review gives every procedure in your project a verdict.

The Protection Review in VBA Padlock Studio, listing each module and procedure with its verdict
The Protection Review, before you ship. Click to enlarge.
How VBA Padlock decides what moves into the DLL and what stays in the Office document
Element Verdict Why
Procedures and class modules -> DLL Compiled to bytecode and removed from the document
UserForms VBA (form) UserForm modules cannot run in a DLL
Document modules VBA (document) Office instantiates these modules itself
Event handlers VBA Must stay in the host module so Office can raise the event
Calls a procedure that stayed VBA Reported as depending on that procedure, by name
Shares module-level state VBA Reported as shared module-level state, with the variable named
Uses an unqualified host global VBA The protected DLL cannot resolve that host object
The VBAPLBridge module VBA It is the bridge itself, and the document has to be able to call it

Anything left in VBA is code you can still act on. When the Review shows a procedure staying behind because it handles an event or shares module-level state, the usual fix is to keep the thin part in the document and move the body into a procedure that compiles. You decide what ships, with the verdicts in front of you.

VBA language compatibility Protection Review reference

Licensing and activation, built into the DLL

The protection and the licensing are the same build. Your compiled DLL can require a key, run as a trial, bind to a machine, and check in with your own server, without you writing an activation dialog.

  • Built-in activation dialog, no extra UI code to write
  • Hardware-locked keys, so a key cannot be shared between machines
  • Full, Trial, Subscription, and Feature-based license models
  • Built-in key generator with batch export
  • Optional online activation with the included PHP kit, running on your own server
  • Deactivation support, so a customer can move a license to a new machine

Licensing reference

The licensing configuration tab in VBA Padlock Studio

From project to shipped file

Produce writes a protected copy next to your source and never modifies the original. The Distribution tab then assembles exactly what your customer needs: the protected file and its bin folder, in the layout the bridge expects.

  • Produce writes <name>_protected next to your source, leaving the original untouched
  • Test Run produces the file and opens it in Office in one step
  • One-click ZIP with the correct bin/ structure
  • Built-in installer generator for a professional setup experience
  • Distribution warns you before shipping an unprotected source file

What to ship

The Distribution tab in VBA Padlock Studio, showing the files prepared for shipping

Ready to Monetize Your VBA Projects?

Download VBA Padlock and start selling protected Office solutions. One-time purchase, no royalties, no subscription.