The High preset is labeled for critical business logic and VM-oriented protection. That label makes it tempting to open every High switch the first time you try the level. The documented defaults are more conservative than that impulse, and they are the right first measurement: verify that your account can use High, generate a build with the documented baseline, and only then consider a single extra option.
I help promote MeowShield. This article is about using the High preset the way the public docs describe it, not about treating High as a pile of untested toggles.
What High actually starts with
Docs describe High as VM-oriented protection for critical business logic. The documented path is: switch to High, verify account permissions, then click Obfuscate. Access to High, and to some of the switches under it, is permission-based. A disabled control is not a prompt to invent a workaround.
The documented High defaults in Docs are:
- instMerge: ON
- instShuffle: ON
- instClosure / instExtract: OFF
- VM anti-debug options: OFF by default
- vmAuth: OFF, with vmExpiry prefilled
If you later call the authorized API from a server or CI job, the same starting point shows up under options.mode set to high, with wire names that do not always match the Playground labels. instrMerge and instrShuffle default to true. A long list of other High fields default to false, including instrClosure, instrExtract, instrDedupe, ifToLogical, encryptString, antiLLM, bogusControlFlow, the runtime-polymorphism flags, selfDefending, highPerfVM, debugProtection, disableDevTools, runOnlyInBrowser, and enableTimeAuthorization. expiryTime is a prefilled Unix timestamp in milliseconds; it is used together with enableTimeAuthorization, which stays off until you deliberately enable it.
I am not going to invent a ranking of those extra switches, or a universal runtime cost for combining them. The public docs describe what the fields do. They do not tell you to enable them all on the first High build.
The two on-by-default switches are the baseline
instrMerge merges VM instructions into larger super-instructions. instrShuffle shuffles VM instruction order to reduce reconstruction readability. Those two are the documented starting point. instrClosure is documented as an alternative to instrMerge when the deployment permits it, and it defaults to off. "Alternative" is not the same as "also turn this on." instrExtract also defaults to off.
The rest of the High surface is optional and, in the documented defaults, off. Anti-debug and environment restrictions can interfere with legitimate debugging, test runners, or non-browser hosts. Time authorization in the generated artifact is a client-side check, not a license server. Self-integrity checks need careful validation of any post-processing you still run. None of these is a substitute for server-side authentication and authorization. Secrets, entitlements, and charges still belong on a server you control.
No protection is absolute. The goal is to increase analysis cost while preserving the behavior you need.
Measure High as a single change
Do not jump to High by stacking it on an already experimental Low or Medium configuration. Start from a real JavaScript file you already know how to test — the distinctive logic you actually intend to protect, not an entire application bundle full of vendored libraries. If you have a working lower-level baseline, generate High with the documented defaults only, then compare.
A useful sequence is:
- Confirm that your account can use High, then generate output with the documented defaults only.
- Run the behavior you care about in the environments you support. If the artifact must also load outside the browser, do not enable a browser-only restriction in order to "make High stronger."
- Compare output, runtime behavior, and file size against the baseline, as the Playground docs already ask you to do.
- Enable at most one extra High switch at a time, and keep it only if the extra analysis cost is worth what you measured.
If the build breaks, official troubleshooting still applies: lower the protection level or disable some options, then add them back one at a time and re-test. If it still fails, contact [email protected] with the configuration, runtime environment, and error details.
When you move the same build to the authorized API, call POST https://meowshield.com/api from a backend or CI runner. Keep apiToken in a server-side or CI secret. Do not put the token in public browser code. Use the current field names at https://meowshield.com/api-docs rather than inventing parameters. API and Playground usage count against the same account quota; confirm current limits with the deployment used by your account, and do not copy a number from memory.
High is a permissioned preset with a documented, relatively conservative default set. It is a poor place to enable every VM and anti-debug switch on the first run.
If you want to inspect the High defaults next to a real file, after you can enable the preset, start at https://meowshield.com.
Top comments (0)