jPSXdec: a PlayStation 1 video converter that gets colours and frame rate right

The gap it fills is colour conversion done wrong

jPSXdec is a modern, cross-platform PlayStation 1 audio and video converter, and it also supports extracting files and TIM images. The list of advantages it claims over the legacy tools of the past starts with output quality and the number of unique movie types it handles, but the sharpest of the claims is the third: it converts with the correct colours, and most legacy tools did this incorrectly. That is a specific, technical complaint rather than a vague claim of being better, and it tells you the author spent time comparing output against reference footage. Two more claims follow in the same register: more accurate frame rate detection, and support for Windows, Mac and Linux, with the source code available and the tool usable from the command line. The PlayStation 1 video format is STR, and a STR file holds interleaved video and XA audio, so a converter that handles the format properly is doing two jobs at once. For a modder or a preservationist this is the difference between a file that looks right and one that looks washed out or plays back at the wrong speed.

Downloading is a release zip, and the newest build is labelled beta

The project ships as release archives on GitHub, and the README links the v2.1 cross-platform release zip directly, with a pointer to a changes file for what is new. The release history makes the maturity picture clear. The listed releases are v2.1, which is marked as a beta at revision 4378 and dated 17 May 2026, v2.0 at revision 4335 dated 16 October 2023, and v1.06, itself a beta, at revision 4156 dated 19 February 2022. So the current build is a beta, and the previous stable line is nearly three years older. The revision numbers are in the release names, which is the convention of a long-lived project where the tag carries more than a version string. The last push to the repository was on 2026-05-17, the same day as the v2.1 release, so the tree at that point reflects the released build rather than something ahead of it. The homepage is the project's blog at jpsxdec.blogspot.com, which is where the release announcements and format notes have historically lived, and the repository also carries a CONTRIBUTING.md and a laintools/ directory alongside the main jpsxdec/ source directory.

The modding story is replacement, not just extraction

The section for developers and modders is the part that distinguishes jPSXdec from a plain transcoder. The tool offers the ability to replace XA audio, video and TIM images, which means you can substitute content into an existing PlayStation 1 stream rather than only pulling content out of it. The README is honest that some programming skill is required and points to the manual for details, so this is a supported workflow for people who are prepared to read documentation, not a one-click feature. Three supporting documents are named. The PlayStation 1 STR video format is described as now well documented, with the latest version of that description at PlayStation1_STR_format.txt inside the jpsxdec directory. There is also a design document, jPSXdec-design.md, and a changes log, CHANGES.txt under the doc directory. Having the format specification published alongside the tool is what makes third-party work on PlayStation 1 media possible at all, and it is the reason the project lists reverse engineering among its topics. The tool is written in Java, which is a practical choice for a tool that has to run identically on Windows, Mac and Linux, since the runtime is available on all three.

The licence allows non-commercial use, and that is the boundary

The licensing position is the single most important fact for anyone considering this tool outside personal use, and the README states it directly: jPSXdec is free for non-commercial use, with the terms living in a LICENSE.txt file under the jpsxdec doc directory. The repository's own licence field carries no recognised identifier, so the practical reference is that file and that statement rather than any badge. A tool that is free for non-commercial use is not the same as open source under a recognised licence, and the two are used interchangeably far too often. What this means in practice depends on what you intend to do. Using the converter to rip your own discs, to study the format, or to work on a personal project is squarely inside what the licence permits. Using it in a paid product, in a commercial modding effort, or as part of a service someone charges for is a different question, and the README does not address it. If you have any commercial intent, read LICENSE.txt before you build a workflow around it, and if the terms are unclear, treat that as a reason to look for a different tool rather than a reason to assume it is fine.

Command-line use is the escape hatch for batch work

Among the listed advantages is that jPSXdec is usable from the command-line, described with a parenthetical for those so inclined. That single line is what separates a converter you drive by hand from a component in a pipeline, and it matters for the people this tool attracts. A preservationist with a shelf of discs can script the conversion, compare outputs, and re-run the batch after a bug fix. A modder replacing audio in a set of tracks can drive the replacement from a script instead of clicking through a dialog per file. The README does not document the command-line interface itself, and the repository listing shows no shell script or CLI directory at the top level, so the details are in the manual and in the jpsxdec source tree rather than in the README. That is a genuine gap for a reader deciding whether to adopt the tool: there is no sample invocation to copy from the documentation the repository ships. What the repository does show is the documentation set that would answer it, with the manual referenced for the replacement workflow, the CHANGES.txt file for behaviour changes between revisions, and the design document for how the converter is put together.

Comparing jPSXdec means comparing against tools that no longer run

The competitors named in the README are not other modern converters but the legacy tools of the past, which is a deliberate framing and it shapes the trade-offs. Legacy PlayStation 1 STR tools were built for Windows in an era when that was the only desktop, so the cross-platform point alone disqualifies them for anyone on Mac or Linux. Their correctness problems are the deeper issue: a converter that gets the colours wrong or misdetects the frame rate produces output that looks plausible and is subtly unusable, and fixing that afterwards means going back to the source disc. A tool that also handles more unique movie types is valuable precisely because the odd formats are the ones that break naive converters. The real alternative is not a different open source converter but a different approach, which is to work from the format specification yourself with ffmpeg and a set of custom decoders, or to use a general purpose tool that will not know anything about STR frame structure. The trade is control against effort. jPSXdec gives you a tested, documented implementation of the format for free, and the cost is that you are inside a project whose latest build is a beta and whose licence stops at non-commercial use.

Editorial conclusion

jPSXdec suits anyone holding PlayStation 1 STR video, XA audio or TIM images who needs a conversion with correct colours and reliable frame rate detection, particularly on Linux and Mac where the older Windows-only tools do not run. It is the wrong choice for commercial work, because the project states it is free for non-commercial use, and it is the wrong choice if you need batch automation without writing code, since the command-line mode is aimed at people who will read the manual. Verify first which revision you are running, since v2.1 is labelled a beta while v2.0 dates from 2023, and read the CHANGES.txt and design notes before replacing an existing conversion pipeline.

Frequently asked questions

Official sources

1. Issues
2. m35/jpsxdec on GitHub
3. Project website
4. README
5. Releases