pspunk.com

pspunk.com covers converting video files for PSP playback as one of its guides, and the process is straightforward: you take a source video, convert it to a format the PSP's hardware decoder handles natively, and copy the result to the Memory Stick in the correct folder. The main constraint is format — the PSP does not play arbitrary video files, so conversion is required rather than optional. This guide covers the general workflow, the format requirements, and the points where people usually get stuck.

What the PSP actually plays

The PSP's video playback is handled by Sony's own decoder, which expects specific container and codec combinations. In practice:

• Container: MP4 (the PSP also supports its own MPS-based formats, but MP4 is the practical target for converted video)
• Video codec: H.264 / AVC at a resolution the PSP can handle — 480×272 is the native screen resolution, and 720×480 is the maximum the hardware accepts for full-screen playback
• Audio codec: AAC
• File placement: the VIDEO folder on the Memory Stick (or the equivalent folder on the storage you're using)

Anything outside these parameters either won't appear in the XMB's Video menu or will fail to play. This is why a straight file copy of a downloaded MP4 often doesn't work — the file may be an MP4 container but use a codec profile the PSP rejects.

The conversion workflow

Step 1: Identify your source file

Check the container and codecs of the file you want to convert. If it's already H.264/AAC in an MP4 container at a supported resolution, you may be able to skip conversion entirely and just copy it across. If it's MKV, AVI, WebM, or uses a different codec (DivX, Xvid, VP9, HEVC), conversion is required.

Step 2: Pick a converter

Any video transcoder that lets you set the output container, codec, resolution, and bitrate will work. The important thing is manual control over the output settings — preset "PSP" profiles exist in some tools but are often outdated or set the wrong resolution. If you're using a command-line tool, you're setting the same parameters you'd set in a GUI.

Step 3: Set the output parameters

Keep the aspect ratio in mind: 480×272 is 16:9, so widescreen sources fit without letterboxing, while 4:3 sources will need padding or cropping. Getting this wrong is the most common cause of stretched or squashed output.

Step 4: Convert

Run the conversion. Expect the output file to be considerably smaller than the source if you're converting from a high-bitrate file, since the PSP's screen doesn't benefit from high resolutions.

Step 5: Copy to the PSP

Connect the PSP via USB (or put the Memory Stick in a reader) and copy the converted file into the VIDEO folder. If the folder doesn't exist, create it at the root of the Memory Stick. Disconnect safely, then check the Video menu on the XMB — the file should appear by name.

Common problems

The file doesn't show up in the Video menu. Almost always a container or codec mismatch. Re-check that the output is MP4 with H.264 video and AAC audio, not just "MP4."

The file shows up but won't play. Usually a resolution or profile issue — the PSP is picky about H.264 profile level. Try re-encoding at a lower level or at 480×272.

Audio plays but video doesn't (or vice versa). One of the two streams is in an unsupported codec. Re-encode both streams rather than copying one through.

Playback stutters. Bitrate is too high for the Memory Stick's read speed, or the resolution is above what the hardware handles comfortably. Lower the bitrate or resolution.

The file plays but looks stretched. Aspect ratio mismatch — the source wasn't 16:9 and wasn't padded to fit.

Is it worth doing

pspunk's own framing is honest about this: most people no longer have a practical reason to watch video on a PSP when phones and streaming exist. The guide is aimed at people who specifically want to load the device with TV shows or films — for a long trip, for the novelty, or because the PSP is the screen they have. If that's you, the workflow above is the whole process; the only real skill involved is getting the output settings right the first time so you're not re-encoding repeatedly.

For related PSP tasks, pspunk also covers custom firmware installation, CXMB custom themes, converting PSX games with PSX2PSP, and creating Atrac3 (.AT3) files for custom XMB sounds — all of which assume custom firmware is already installed.

pspunk.com is a PSP information and guides site. It publishes walkthroughs and resources for custom firmware, firmware downgrading, custom themes, homebrew tools, and related media tasks. It is aimed at PSP owners who want to modify, personalize, or get more use out of their console.

What the site covers

The site's own description lists custom firmware installation, firmware downgrading, custom themes, and homebrew tools. The current homepage headings show how that plays out in practice:

There is also a community showcase page ("May 2026 Showcase") where users share photos of their PSPs, described as a recurring competition intended as inspiration.

Who it is for

The content assumes a PSP owner who is willing to install custom firmware or plugins. Several pages state prerequisites directly rather than treating them as optional:

• Custom themes require custom firmware, with ARK4 described as preferred.
• Converted PSX titles require custom firmware to play.
• The ARK page notes that new users only need to review installing plugins and updating ARK when a new version appears.

If you only want to play original games on an unmodified PSP, most of the site's core material will not apply to you.

How to use it

1. Identify your goal first — firmware setup, a plugin, a theme, or a media conversion.
2. Open the matching guide and read the prerequisites before starting. The downgrader page explicitly warns that updating or downgrading firmware and installing custom firmware always carry some risk, and asks readers to read the steps carefully.
3. Follow the steps in order, since these guides chain together — for example, CXMB themes depend on custom firmware, which depends on the ARK or downgrade guides.
4. Check back for version updates. The ARK page treats updating to a new release as a routine step rather than a one-time install.

Limits to keep in mind

The site is a guide collection, not a store or an official Sony resource. Nothing in the available material indicates pricing, accounts, or paid tiers, so treat it as documentation rather than a service. Firmware modification carries risk of rendering a console unusable, and the site itself flags this on the downgrader page — back up what you can and follow each guide's warnings before proceeding.

Installing custom firmware (CFW) on a PSP means replacing or augmenting the official Sony firmware so the console can run homebrew, plugins, custom themes, and converted PSX games. The exact steps depend on your current firmware version and PSP model, so the safest approach is to identify your starting point first, then follow a guide written for that specific version. pspunk.com is a resource site that publishes these guides, covering custom firmware installation, firmware downgrading, custom themes, and homebrew tools.

Before You Start: What You Need to Know

Custom firmware installation carries real risk. The pspunk.com Chronoswitch Downgrader page states plainly: "There are always some risks when updating(downgrading) your firmware or installing custom firmware." A failed or interrupted flash can leave a PSP unable to boot normally.

Conditions to confirm before touching anything:

• Your current firmware version. This determines which method applies. A PSP already on custom firmware updates differently than a stock PSP.
• Your PSP model. Different hardware revisions have different CFW options and limits.
• A stable power source. Do not attempt a flash on a low battery. A power interruption mid-write is one of the most common ways to brick a console.
• A way to recover. Know whether your model supports recovery mode before you begin.

If you are new to this, the pspunk.com ARK page notes that for new users "the only thing to review would be installing plugins and updating ARK when a new version is available" — meaning once CFW is running, day-to-day use is mostly about plugins and version updates, not repeated flashing.

The General Process

The broad sequence for a stock PSP is:

1. Identify your firmware version in the PSP system settings.
2. Check whether a downgrade is required. Some firmware versions must be brought down before CFW can be installed; the Chronoswitch Downgrader guide covers this scenario.
3. Prepare the memory card with the required files for your firmware version.
4. Run the installer from the PSP and follow the on-screen prompts without interrupting power.
5. Verify that the system boots and reports the new firmware.
6. Install supporting tools such as plugins, then test with a known homebrew application.

Each of these steps has version-specific detail that a generic summary cannot cover safely. Use the guide matching your exact firmware rather than adapting instructions from a different version.

Recommended Firmware: ARK

pspunk.com documents ARK-4 and ARK-5 in a dedicated "Usage and Tips" page, which covers installing plugins, using features, and basic setup. ARK is presented as the practical CFW choice, and the CXMB custom themes guide lists custom firmware as its only requirement, noting "ARK4 would be preferred."

What ARK gives you in practice:

• Plugin support — the mechanism behind most quality-of-life additions.
• Custom themes — via the CXMB plugin, using .CTF format theme files.
• PSX game support — converted PSX titles require custom firmware to run.
• Ongoing updates — ARK receives new versions, and updating is a routine task once installed.

What Custom Firmware Unlocks

Once CFW is running, these are the common additions documented on the site:

Common Pitfalls

• Skipping the version check. Instructions for one firmware version applied to another is the most frequent cause of failed installs.
• Interrupting power. Do not let the battery die or remove the memory card during a flash.
• Assuming converted PSX games just work. They require custom firmware; the conversion step alone is not enough.
• Forgetting plugin placement. Plugins and themes go in specific folders, and a misplaced file simply won't load.
• Not planning for updates. ARK releases new versions; know how to update before you need to.

Where to Go Next

Start with the guide that matches your current firmware version and PSP model, not a general tutorial. pspunk.com organizes its content by task — CFW usage and tips, downgrading, plugins, themes, and conversions — so you can go directly to the page covering your situation. If you are unsure which firmware you have, check the system settings first; that single detail determines everything that follows.

Chronoswitch is a PSP downgrade tool covered on pspunk.com for users who need to move their console to an older firmware version. According to the site's Chronoswitch Downgrader page, it can help in specific scenarios where a downgrade is required, and the page stresses reading the steps carefully because there are always risks when updating, downgrading, or installing custom firmware. If your goal is simply to run current homebrew, a downgrade may not be necessary; Chronoswitch is for cases where a lower firmware is genuinely needed.

What Chronoswitch Is For

The pspunk.com description frames Chronoswitch as a downgrader rather than a general firmware installer. Its purpose is to take a PSP from a newer firmware to an older one. The site notes it "can be helpful in the following scenarios," but the excerpt does not list those scenarios in detail, so treat the tool as a targeted solution rather than a routine step.

A downgrade is different from installing custom firmware. Custom firmware pages on the site, such as the ARK-4 and ARK-5 guide and the CXMB custom themes page, assume you already have compatible custom firmware in place. Chronoswitch addresses the firmware version itself.

Before You Start

The site's own warning is the most important preparation item: "There are always some risks when updating(downgrading) your firmware or installing custom firmware." Plan around that.

• Confirm your exact current firmware version and your PSP model, since not every model or version supports the same downgrade path.
• Check the Chronoswitch page on pspunk.com for the specific scenarios it lists, and make sure yours matches.
• Read the full step list before touching the console. The page explicitly says to read carefully through the steps.
• Understand that a failed or interrupted downgrade can leave the console in a worse state than before.

The excerpt does not specify required firmware ranges, supported models, or file names, so verify those on the live page rather than assuming.

General Downgrade Flow

Because the excerpt does not reproduce the exact menu steps, the sequence below describes the shape of the process. Follow the numbered steps on the pspunk.com page for the precise actions.

1. Identify your target firmware. Decide which older version you actually need, based on the homebrew or plugin you intend to run.
2. Gather the required files as listed on the Chronoswitch page. The excerpt does not name them, so use the page's list.
3. Prepare the memory card with those files in the locations the guide specifies.
4. Run Chronoswitch on the PSP and follow its on-screen prompts.
5. Let the process finish without interruption. Do not power off or remove the memory card mid-downgrade.
6. Verify the new firmware version in the PSP system settings after it completes.

Expected result: the console reports the older firmware version, and you can then proceed with whatever the downgrade was meant to enable.

Common Pitfalls

• Skipping the scenario check. If your situation isn't one the tool is meant for, the downgrade adds risk without benefit.
• Wrong files or wrong locations. A downgrade that can't find its files may fail partway.
• Interrupting the process. Losing power or pulling the card during a firmware write is the classic way to brick a console.
• Assuming a downgrade equals custom firmware. After downgrading, you may still need to install custom firmware separately; the site's ARK and CXMB pages cover that side.

After the Downgrade

Once you're on the older firmware, the rest of pspunk.com's guides become relevant: ARK-4 and ARK-5 for custom firmware usage and plugins, CXMB for custom themes, Game Categories Lite for organizing games and homebrew, and PSX2PSP for converting PSX titles. If your only reason for downgrading was to run one of these, confirm the target firmware actually supports it before starting.

To use custom PSP themes, you need custom firmware installed (ARK-4 is recommended by pspunk), the CXMB plugin, and a theme in .CTF format. CXMB replaces the PSP's default theme handling so the system reads custom .CTF files instead of the built-in themes. The plugin and the theme files are separate pieces: CXMB is the loader, and .CTF is the content you load. Without custom firmware, CXMB cannot run, so that is the first prerequisite.

What CXMB Does and What It Requires

CXMB is a plugin that lets the PSP load custom themes in .CTF format. According to pspunk's CXMB guide, the only requirement is having custom firmware, with ARK-4 described as the preferred option. The guide also points to its own ARK-4 installation page for getting custom firmware onto the system.

Two things follow from that:

• Custom firmware is mandatory. CXMB is a plugin, and plugins load through custom firmware. On official firmware there is no supported way to run it.
• The theme must be .CTF. CXMB does not convert other formats. If a theme is not already .CTF, it is not ready to use with this plugin.

Installing CXMB and Applying a Theme

The exact menu path depends on your custom firmware, so treat the steps below as the general flow rather than a fixed click sequence. The expected result at the end is that the XMB displays the custom theme after a restart.

1. Confirm custom firmware is running. If it is not, install it first. pspunk's CXMB page links to its ARK-4 install guide for this.
2. Get the CXMB plugin files and place them where your firmware loads plugins from (commonly a seplugins folder on the memory card).
3. Enable CXMB in your firmware's plugin configuration so it loads at startup.
4. Place the .CTF theme file in the location CXMB reads themes from.
5. Select the theme through CXMB's theme selection, then restart the PSP so the theme is applied.

If the theme does not appear after restarting, the usual causes are that CXMB is not enabled, the .CTF file is in the wrong folder, or the theme was built for a different firmware version.

Where Custom Themes Fit Alongside Other PSP Customization

pspunk groups custom themes with several other customization tasks, and it helps to know which ones are related:

The common thread is custom firmware: themes, PSX conversions, and most plugins depend on it, while video conversion and Atrac3 file creation are more about preparing the right file format.

Practical Notes Before You Start

• Match the theme to your firmware. A .CTF built for one firmware version may not display correctly on another, which is a common reason a theme "doesn't work" even when CXMB is set up right.
• Keep a way back to the default theme. Since CXMB changes how themes load, disabling the plugin or removing the theme file should return you to the standard XMB appearance.
• Custom firmware carries risk. pspunk's downgrader page notes there are always risks when changing firmware or installing custom firmware, so install custom firmware before CXMB rather than treating the two as one step.

If your goal is only to change how the PSP looks, CXMB plus a .CTF theme is the direct route. If you also want custom sounds on game entries, that is a separate Atrac3 step, and if you want your games sorted into folders, that is the Game Categories (Lite) plugin instead.