Protect attribution and add reference-aware naming and code transformations to Vortex Studio projects. Your project stays on your device.
01
Your project
Choose a Vortex Studio .vrtx file
——
◈
Private by design. Files are processed in your browser with no backend upload. The compression library is loaded from a public CDN.
02
Watermark features
Choose the transformations to apply
Instance renaming
Renames editable instances and rewrites resolved Luau references. Core services and protected components are excluded.
Function renaming
Targets eligible, non-ambiguous local functions only.
Variable renaming
Targets safe single-variable local x = … declarations.
Additional protection
03
Watermark & export
Make a new file; never overwrite your original
Format supportVRTX v5 only
ProcessingClient-side
ValidationBinary structure check
Optional Studio source preparationExperimental
Only for Code Virtualization / decoy Script instances: Select either option, then click Step 1. Download the prepared .vrtx, open and SAVE it in Vortex Studio, re-upload the Studio-saved copy and click Watermark project. No manual placeholder creation is normally needed, but the Studio save is still required for this experimental workflow. If compatible slots are already in your file, go straight to Watermark. If you skip preparation without existing slots, these two features are skipped.
Experimental reverse-engineered editor. Automatic slot PREPARATION is available, but directly injecting executable ModuleScripts and decoy Scripts in a finished project remains disabled because earlier builds crashed. Keep backups and playtest in Vortex Studio.
✓Watermark file generated
Instances—
Renamed instances—
Updated script references—
Unused function blocks added—
Local functions renamed—
Local variables renamed—
Severe literal rewrites—
!
Compatibility matters more than aggressive obfuscation.
Instance references including spaced names are now rewritten when resolvable. Computed keys, reflective lookups, engine-native names or unrecognized binary records still cannot always be proven safe. Optional client-only teardown is destructive to the current client session. It is disabled by default and cannot guarantee protection against a modified client. Playtest in Vortex Studio before replacing your original.
