What is the VBE file format?
.vbe files are closely related to VBScript - a scripting language based on Microsoft's Visual Basic. A .vbe file is a script file written in VBScript that has been passed through Microsoft's Script Encoder (screnc.exe). The file stores the script's source code in encoded form so that it cannot be directly read or edited; the encoding is a reversible obfuscation rather than true encryption. .vbe files are executed by Windows Script Host (wscript.exe or cscript.exe) and are only supported on Windows operating systems.
Encoded .vbe files are identifiable by the distinctive delimiters #@~^ (opening) and ^#~@ (closing) that wrap the obfuscated payload along with a length checksum - there is no binary magic number.
.vbs is the plain-text equivalent used in the Visual Basic Script environment. The main difference between those two formats lies in encoding - a .vbe file is encoded, whereas a .vbs is not. The same Script Encoder tool also produces .jse files, the encoded counterpart for JScript. Both encoded formats can be embedded inside a .wsf Windows Script File.
.vbe files are commonly used by malicious actors as a means of distributing malware via email, since the encoding obscures the payload from casual inspection. Opening unknown attachments containing a .vbe file should be handled with the utmost caution. More advanced users may decode and inspect the source code using a community decoder script - such as a Decode.vbs utility - before executing anything.
Security & safety
RISK: HIGH.vbe is a classic Windows malware-obfuscation format. Like .vbs, double-clicking a .vbe RUNS it immediately with your privileges via Windows Script Host - it can delete files, edit the registry, download payloads or spread itself, and the encoding deliberately hides what it does. The "encoding" is trivially reversible, so it protects nothing and is mainly used to evade simple scanners and casual inspection. Rules: never run a .vbe that arrived by email, chat or download unless you wrote it or fully trust it; to inspect one, DECODE it to VBScript and read it as text - never double-click; be suspicious of double extensions like 'invoice.pdf.vbe'. Because of this history and VBScript's deprecation, many environments block .vbe outright. An unexpected .vbe should be treated as hostile and deleted.
Format details
in a nutshellPrograms that open VBE files
Windows3 apps
Script decoder + Notepad/Notepad++/VS Code
Free To READ a .vbe safely, DECODE it first (e.g. a public Script Decoder), then open the recovered .vbs in Notepad/Notepad++/VS Code. Never double-click the .vbe to inspect it - that runs it. 
Visual Studio Code
Free Open the decoded VBScript with syntax highlighting to understand what the script does before deciding anything.
Windows Script Host (wscript / cscript)
Built-in To RUN a trusted encoded script: double-click (wscript) or 'cscript script.vbe' - WSH decodes and executes it. Only for code you fully trust; it runs with your privileges. On Windows 11 24H2 the optional VBScript feature must be present. 
macOS1 app
Any text editor (after decoding)
Free macOS cannot RUN VBScript (no Windows Script Host). You can only decode and read the source - open the decoded text in TextEdit or VS Code. 
Linux1 app
Any text editor (after decoding)
Free Linux has no VBScript runtime; only decode-and-read is possible. Open the decoded source in VS Code/gedit. Technical details
deep spec| Developer | Microsoft |
| Format type | Encoded (obfuscated) VBScript source file |
| Encoding method | Proprietary character-substitution obfuscation with an embedded checksum; not true encryption - fully reversible |
| File structure markers | Encoded payload wrapped between `#@~^` (open) and `^#~@` (close) delimiters with an embedded length/checksum field |
| Runtime engine | Windows Script Host - executed by `wscript.exe` (GUI) or `cscript.exe` (console) |
| Encoder tool | Microsoft Script Encoder (`screnc.exe`), a free command-line utility |
| MIME type | `text/vbscript` / `application/x-vbe` |
| Platform support | Windows only; WSH is a built-in Windows component |
| Default file association | Registered to execute via WSH on double-click in Windows Explorer |
| Security risk | High - encoding hides payload from casual inspection; widely exploited in email-based malware delivery |
| Decoding | Fully decodable back to plain `.vbs` using publicly available community decoder scripts |
| Script language version | VBScript 5.x - same language engine as plain `.vbs` files |
| Character encoding | ASCII/ANSI text; the obfuscated block uses only printable ASCII characters |
| Plain-text equivalent | `.vbs` (unencoded VBScript); encoded JScript counterpart is `.jse` |
| Released | Late 1990s - produced by Microsoft Script Encoder (screnc.exe), alongside VBScript/WSH |
| Specification | learn.microsoft.com |
VBE conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about VBE files.
