VCTool supports a wide range of interfaces (VCI):

• VAS5054x / VAS6154x, using the standard VW/Actia D-PDU API driver. Stable operation with clone/fake interfaces is not guaranteed.

• Scanmatik SM2/SM3. Full support is available for both the J2534 driver and the ISO 22900 D-PDU driver supplied by the manufacturer. When using the D-PDU driver, communication over CAN (SM2/SM3) and DoIP (SM3 only) protocols is supported. 

• For the MQBevo*, MLBevo, MEB, PPC, and PPE platforms, the eNet interface can be used via the DoIP protocol.

• Any high-quality J2534-compliant interface that supports the ISO 15765 CAN UDS protocol, such as Tactrix Openport 2.0, Chipsoft, Scanmatik SM2/3, etc. The use of copies of well-known brands sold through dropshipping stores is not recommended.

• ELM/STN interfaces are no longer supported.

For maximum performance, we recommend using eNet, VAS5054/6154, Scanmatik SM2/3 or J2534 interfaces.

J2534 and VAS5054 interfaces are supported only in the x86 version of the application, as x64 drivers are not available for them.

Some J2534 interfaces can be used in the x64 version of VCTool via the D-PDU API driver; however, this approach reduces interface performance by approximately 2–3 times compared to using the native driver.

We strongly advise against using VxDiag / VCX interfaces. Their use may lead to unpredictable results and is entirely at your own risk.

* Support for the DoIP protocol on the MQBevo platform depends on the vehicle configuration.

VCTool works with almost all vehicles built on the MQB, MQBevo, MLBevo, PPC, PPE and MEB platforms. You can see the list of supported vehicles by launching VCTool and opening the “About” section.

VCTool provides partial support for the PQ, PL, and MLB platforms through the TP20 protocol. These platforms are significantly outdated and are not a priority for development, therefore we do not plan to expand support for older vehicles.

The Porsche brand is not officially supported in VCTool for diagnostics.
However, you can work with these vehicles in MLBevo platform compatibility mode, and also use the Porsche Security Lock module to make manual configuration changes (not applicable to vehicles with SFD2).

Although we do not offer trial periods, you can create an account and try VCTool without payment—some features will be available in a limited mode.

VCTool is the world’s first third-party application that allows you to unlock control units protected by SFD in real time! You can read more about how to work with SFD here.

The SFD token generation service is provided by a third-party organization and may be unavailable due to reasons beyond VCTool’s control. You can monitor the service status on the status page.

The generation of SFD tokens are not included in any subscription and are provided for an additional fee!

Starting from version 1.16.1.0, dated January 17, 2024, VCTool fully supports working with the SFD2 system in manual mode (without automatic token generation—the user is responsible for this process), uploading .XML packages containing SFD2 tokens, and simulating SFD2 in the UDS ECU Simulator.

SFD2 has nothing to do with SFD v1 and works completely differently, so the concept of “SFD2 Unlock” is not applicable to it. In SFD2, a token is permission to write specific data defined in the token, meaning any data set (adaptations, datasets) you want to write to the control unit must be signed on the VAG server and only then written to the control unit.

At the moment, VCTool fully supports working with the SFD2 system in manual mode only, so, you can gather the necessary data, but obtaining the token is the user’s responsibility.

No, VCTool does not support binding control units to a vehicle, removing component protection, or working with the immobilizer.

Yes. VCTool is a client-server application and most of the information needed to work is stored on our server.

The Internet connection is used only during the login process and download of data (for example, backups, datasets or other data), so if, for example, the connection to the Internet is lost during the firmware update of the control unit, this will not affect the process in any way.

We strongly advise against performing remote diagnostics via USB port forwarding or VPN‑DoIP. These types of connections do not meet required standards for reliability, speed, or stability and can lead to unpredictable consequences, including damage to control units. Any such operations are carried out at your own risk, and you assume full responsibility for them.

Our Terms of Use prohibit transferring a single user account between different PCs. Account transfer is permitted only when the working PC is fully replaced or when its hardware configuration has been changed.

However, the account may be linked to a YubiKey hardware security key through the Mobility Add-on module. In this case, the account can be used on any PC where the hardware token is connected.

For more details, please refer to the Account Policy.

Yes, but only if your account is linked to a YubiKey hardware security key through the Mobility Add-on module.

Commercial accounts are normally linked to the hardware ID of a physical PC or laptop. Virtual machines may change or emulate hardware identifiers, so standard PC binding cannot be used for VM-based authorization.

Starting from May 1, 2026, VCTool authorization inside a virtual machine is only possible with a linked hardware key. Without a linked YubiKey, login inside a virtual machine will not be allowed.

The hardware key must remain physically connected to the computer during the entire VCTool session. Only one computer may be used at the same time, and transferring the key or account access to third parties is prohibited.

No, we do not provide this type of support. All requests are accepted and handled only through contact forms and email.

We do not administer and do not have access to any “VCTool support groups” in social networks, messengers, forums, or other third-party communities created by enthusiasts or users.

Please submit support requests, technical questions, and bug reports only through the official support channels. Otherwise, we will most likely not receive them and will not be able to review or respond to them.