WPS Macro Editor on Windows FAQ

Last updated:July 15, 2026

Common questions about WPS Macro Editor usually involve the default development environment, macro-enabled file formats, and cross-platform compatibility; this FAQ includes 4 frequent questions and a glossary.

FAQ

Why does WPS open the VBA editor instead of the JS macro editor?

  1. Click File and open Options.
  2. Open the View tab.
  3. Select Default JS Development Environment and save the setting.
  4. Return to the developer tools area and check whether the JS macro editor now opens first.

Why can’t my macro code be saved?

  1. Check the current file format of the document.
  2. If the file is .docx, change it to a macro-enabled format.
  3. In WPS Writer, save the file as .docm or another format that retains macro code.
  4. Reopen the file and confirm that the macro content is still present.

Why can’t VBA macros written on Windows run directly on Linux or Mac?

  1. Confirm whether the current macro uses VBA or JS.
  2. Review the differences in macro environments and scripting languages across systems.
  3. If you need to continue on Linux or Mac, rebuild the logic with JS macros.
  4. Test the script again on the target system.

What security points should I keep in mind when using the macro editor?

  1. Open only trusted macro scripts or macro-enabled documents.
  2. Confirm the purpose and content before running a script.
  3. Avoid running macro files from unknown sources.
  4. Keep a backup of important documents before testing macros.

Glossary

TermDefinition
JS macroAn automation script written in JavaScript that can be created and maintained in WPS Macro Editor.
Default JS development environmentAn option in WPS settings that makes the developer entry open the JS-related environment first.
Macro-enabled formatA file format that can retain macro code, such as .docm; standard .docx files do not retain macros.
VBA editorA development environment for VBA macros, separate from the JS macro editor.