AutoPlugin 2 for PS Vita: Download, Install (With or Without a PC), and Latest Version Guide

AutoPlugin 2 is a one-click plugin manager for PS Vita and PlayStation TV homebrew, currently maintained by Team OneLua under developer theheroG, after originally being released by jolek back in May 2020. It lets you install, uninstall, update, and configure dozens of community plugins, visual tweaks, controller fixes for PSP games running through Adrenaline, battery-life patches, and custom boot splash screens, all through a simple on-device menu instead of manually editing config.txt files by hand. One requirement before anything else: your Vita needs custom firmware already installed, AutoPlugin 2 manages plugins, it doesn’t jailbreak the console itself. I set this up on my own Vita using the QR code method specifically because I didn’t have a PC handy at the time, and it worked, though not without one hiccup I’ll get into below. Here’s the complete, current breakdown.

What Is AutoPlugin 2, and What You Need Before Installing It

AutoPlugin 2 solves a genuinely annoying problem in Vita homebrew: without it, installing a plugin means manually finding the right file, dropping it into the correct folder, and hand-editing a config.txt file with the exact right syntax, one typo and the plugin either won’t load or worse, causes a boot loop. AutoPlugin 2 turns that into a menu you scroll through and select from, handling the file placement and config editing for you, and it can update both the plugins themselves and the tool’s own language files directly over the internet from the Vita.

Before you do anything else, confirm your Vita already has custom firmware (CFW) installed, typically through HENkaku and Enso for permanent, reboot-persistent homebrew access. AutoPlugin 2 is not a jailbreak tool and can’t get you from stock firmware to homebrew access on its own, it only works once that foundation is already in place. If you’re not sure whether your Vita has CFW installed, check for the HENkaku or VitaShell app icon on your home screen, if it’s there, you’re set to continue.

If you’ve never used it before, VitaShell is the file manager that underpins almost everything in this guide, it’s the homebrew equivalent of a file explorer, letting you browse the Vita’s internal storage (ux0:), memory card mounts, and install VPK packages directly on the device. AutoPlugin 2 doesn’t replace VitaShell, it works alongside it, you’ll use VitaShell to get the initial VPK onto your Vita one way or another, and AutoPlugin 2 takes over from there for actually managing plugins.

Popular AutoPlugin 2 Plugins and What They Do

One thing a lot of guides skip entirely is actually naming what you’re installing once AutoPlugin 2 is running. The tool manages dozens of community-made plugins, and knowing a few of the most commonly used ones by name helps make sense of what you’re looking at in the menu rather than clicking through a long list blind.

Controller and input plugins are some of the most popular: ds4vita and ds34vita by xerpi and MERLev let you use a DualShock 4 or DualShock 3 controller with your Vita over Bluetooth, and reVita, also by MERLev, extends that further with additional remapping options. DSmotion by OperationNT414C brings motion-control support to certain games that expect it.

Visual and quality-of-life plugins cover a lot of ground too. VitaGrafix by Electry lets you adjust resolution and graphical output on supported games, Custom Splash Boot by Princess of Sleeping swaps out the default boot screen for your own image, and NoLockScreen and NoTrophyMsg, both by TheFlow, strip out the lock screen and trophy popup notifications respectively for players who find them intrusive.

PSP and Adrenaline-specific plugins, relevant if you’re emulating PSP games through Adrenaline, include RemasteredControls, also by TheFlow, which patches control schemes for PSP titles running under Adrenaline, and NoPspEmuDrm by Acid_Snake, which handles DRM-related compatibility for certain PSP software running in that emulation layer.

Storage and system plugins round things out: PSVita-StorageMgr by CelesteBlue helps manage storage directly on the device, and usbmc by Yifan Lu enables USB mass storage mode for easier file transfers without needing FTP.

This is a small sample of a much longer list inside the tool itself, dozens of plugins spanning trophy management, battery optimization, keyboard input (VitaKeyboard by mswlandi), and more. The point isn’t to memorize all of them, it’s knowing that each one is independently maintained by its own developer, credited directly in AutoPlugin 2’s menu, which is also why version updates to AutoPlugin 2 itself often bundle version bumps to several individual plugins at once rather than changes to AutoPlugin 2’s own code.

How to Install AutoPlugin 2 on PS Vita (With a PC)

This is the standard method and the one most guides default to.

1. Download the current Autoplugin2.vpk file from the official GitHub releases page.
2. Connect your Vita and PC using either VitaShell’s FTP mode or USB mode.
3. Transfer the VPK file into the ux0:/vpk/ folder on your Vita.
4. Open VitaShell on the Vita, navigate to ux0:/vpk/, highlight Autoplugin2.vpk, and press X to install it.

That’s the whole process, and it takes a few minutes total depending on your transfer speed. If FTP mode feels unfamiliar, USB mode works the same way and just mounts the Vita’s storage like a regular USB drive on your PC, either transfer method gets the file where it needs to go.

How to Install AutoPlugin 2 Without a PC (QR Code Method)

This is genuinely the most useful trick in this whole guide if you don’t have easy access to a computer, and it’s a feature a lot of people don’t realize VitaShell even has.

1. Open VitaShell on your Vita.
2. Press Left D-Pad and Circle together at the same time. This launches a hidden camera-scanning feature built into VitaShell.
3. On your phone, pull up a QR code from an official mirror, PSX-Place or Brewology’s downloader page both provide one for AutoPlugin 2.
4. Point your Vita’s camera at the QR code on your phone screen. VitaShell reads it, downloads the file directly, and installs it, no PC involved at any point in the process.

I used exactly this method the first time I set AutoPlugin 2 up, mostly because my PC was upstairs and I couldn’t be bothered. The scan itself took a couple of tries to register, the Vita’s camera isn’t exactly high resolution, so if it doesn’t pick up the code on the first attempt, try holding the phone a bit further back and steadying your hands rather than assuming the method doesn’t work. Once it does register, the download and install happen automatically and it’s honestly a little satisfying watching it complete without ever touching a computer.

Installing AutoPlugin 2 with SD2Vita

If you’ve got an SD2Vita adapter, meaning you’re running your Vita’s storage off a microSD card rather than (or alongside) an official Sony memory card, there’s a third route. Since the microSD card can be removed and read directly by a PC card reader, you can copy the VPK file straight onto the card without going through VitaShell’s transfer modes at all, then install it from the Vita once the card’s back in. AutoPlugin 2 also specifically supports installing plugins to the ur0: mount point, which matters for SD2Vita setups where certain files need to live on the system’s internal memory rather than the SD card itself, so plugin installs behave correctly regardless of which storage split your setup uses.

Where to Download the Latest Version (and Why You Shouldn’t Trust a Random VPK Link)

The authoritative source is the ONElua/AutoPlugin2 repository on GitHub, mirrored officially through PSX-Place and Brewology. As of the most recent tracked release, the version is 2.19, released in August. That update brought the NoNpDrm Unofficial plugin up to v1.5 under current maintainer SuleMareVientu, refreshed the noled plugin to v2.2 under falkenhawk, pushed the vixen plugin from v1.5 to a major v2.0 revision, added kernel-level support to Vitacompanion through a new vitacompanion_kernel.skprx file, bumped USBDisable to v3.03, and fixed a bug that had been preventing some VPK files from downloading correctly through the in-app downloads section.

That said, don’t treat “2.19” as a number to memorize, homebrew tools like this update on an active, unpredictable schedule, and by the time you’re reading this there’s a real chance a newer point release exists. Always check the GitHub releases page directly for whatever the current version actually is rather than trusting a hardcoded number from any article, including this one. This is also exactly why sticking to GitHub, PSX-Place, and Brewology matters: random third-party download sites hosting old or repackaged VPK files are a common source of outdated, broken, or in worse cases tampered installs in this community.

Common Installation Errors and Fixes

Corrupted file error during VPK installation: This is the most commonly reported issue, and in the vast majority of cases it traces back to a flaky USB transfer rather than a problem with the file itself. Switching to FTP transfer mode instead of USB resolves it in most reported cases. If you hit this error, don’t assume the download is bad, try the transfer again over FTP before redownloading anything.

QR scan not registering: Covered above, but worth repeating as a dedicated fix, hold the phone screen steady and slightly further from the Vita’s camera than feels natural, and make sure your screen brightness is high enough that the code isn’t washed out or too dim to read clearly.

Plugins not appearing after install: Double-check that you’re browsing the correct mount point, ux0: versus ur0:, particularly relevant for SD2Vita users, since a plugin installed to the wrong mount point simply won’t show up where you’re looking for it.

Boot loop after installing a plugin: This is the scariest-sounding issue but usually the most fixable. If your Vita gets stuck cycling at the boot screen after enabling a new plugin, hold the volume-down button while powering on to boot into safe mode, which loads without plugins active, letting you get back into VitaShell or AutoPlugin 2 to disable whatever you just added. This is exactly why the safety advice below about not stacking untested plugins matters in practice, not just in theory.

How to Update AutoPlugin 2 and Its Plugins

AutoPlugin 2 can update itself and its plugin library directly from the device, you don’t need to redownload the whole VPK every time a new version comes out. From the main menu, the Update plugins Online option checks each installed plugin against its latest tracked version and updates anything out of date, and a separate Update Languages Online option refreshes the tool’s translation files the same way. Note the version-2.00 changelog specifically added a rule that automatic plugin updates only run if you’re already on the newest AutoPlugin 2 version yourself, so if online updates seem to be doing nothing, check whether AutoPlugin 2 itself needs a manual update first via a fresh VPK install using any of the three methods above.

How to Uninstall a Plugin (or AutoPlugin 2 Itself)

Removing a plugin works the same way you installed it, open AutoPlugin 2, find the plugin in its category list, and select the uninstall option rather than install, it reverses the config.txt entry and removes the associated files automatically. If you want to remove AutoPlugin 2 entirely, that’s done the normal Vita way, from the home screen, hold the AutoPlugin 2 icon and select delete, the same as removing any other app or game. Note that uninstalling AutoPlugin 2 itself doesn’t automatically uninstall plugins you’d already enabled through it, if you want a clean slate, uninstall the plugins first while AutoPlugin 2 is still installed, then remove AutoPlugin 2 last.

A Quick Look at AutoPlugin 2’s Version History

Since this is an actively developed tool, it helps to see how it’s evolved rather than treating “2.19” as a static fact. Early versions built out the basics: version 1.13 added background music controls and updated several PSP-side plugins, and version 1.29 added Korean language support. Version 2.00 was a meaningful structural update, adding a display for each installed plugin’s actual version number and introducing the rule that automatic updates only run on the current AutoPlugin 2 release. From there, point releases have mostly focused on adding new plugins and updating existing ones: version 2.03 added support for QuickmenuReborn addons and a PS Vita TV-specific Dolcewifi plugin, version 2.06 added a PSP documentation plugin, and the current 2.19 release, covered in full above, refreshed several plugin dependencies including a major vixen update and new kernel-level support for Vitacompanion. The pattern across nearly every release is the same: most updates are about keeping pace with the individually maintained plugins inside the tool, not overhauling AutoPlugin 2’s own core functionality, which has stayed fairly stable since the 2.00 restructuring.

Is AutoPlugin 2 Safe to Use?

Short, honest answer: broadly yes, with one caveat worth knowing rather than ignoring. There was community discussion in the past about AutoPlugin potentially contributing to SD card issues under heavy or overloaded plugin use, stacking many plugins at once, especially ones that weren’t well-tested together. In practice, this isn’t a confirmed widespread issue, and the vast majority of users run AutoPlugin 2 without any card problems at all. The sensible, practical advice that actually reduces risk: don’t install plugins you don’t recognize or don’t actually need, and avoid stacking a large number of them simultaneously just because they’re available. A handful of plugins you understand and actually use is safer and more stable than installing everything in the list at once out of curiosity.

Quick Answers (FAQ)

Getting Started: The Short Version

Confirm your Vita already has custom firmware installed first, that’s non-negotiable groundwork this tool can’t do for you. From there, pick whichever install method fits your situation: PC and USB or FTP if you’ve got a computer handy, or the QR code trick through VitaShell if you don’t. Either way, source the file from GitHub or an official mirror, never a random third-party site, and once it’s running, install only the plugins you actually understand and plan to use rather than everything available at once.

If you’re into retro hardware and homebrew more broadly, it’s worth checking out the rest of what’s covered on the site. And if modern console coverage is more your speed once you’re done tinkering with a decade-old handheld, my guides on Marvel’s Wolverine on PS5 and the real free Sega classic on Xbox cover current-gen console content on the opposite end of the gaming spectrum from Vita homebrew.

Version, authorship, and installation details here were checked against the official ONElua/AutoPlugin2 GitHub repository, PSX-Place’s resource listing, and Brewology’s mirror page. Since this is an actively updated tool, re-check the GitHub releases page for the current version before relying on any specific number, including 2.19 referenced above.