Blu-ray ripping and authoring

Your discs, kept like they matter.

Rip, author, verify and burn Blu-ray discs with native tooling, on macOS, Linux and Windows. Native AACS key recovery, UDF 2.50 images, authored BD-J menus, DVD-Video and 1:1 clones. No MakeMKV, no subscription.

macOS 12+ · Linux x86_64 · Windows x86_64 · MIT · builds on GoFile and file.kiwi

Keepsake Atelier app icon: a small blue keepsake box holding a Blu-ray disc
  • KeysNative AACS1 + AACS2
  • AuthorUDF 2.50, native
  • MenusAuthored BD-J
  • VerifyNavigation + clips
  • Burnhdiutil, guarded
  • AutomateMCP + CLI

What it does

One workshop for the whole disc.

Inspect first, rip losslessly, author something new, then check it before it touches a burner.

Inspect

See the whole disc

Every title, playlist, clip, duration, chapter mark, stream and AACS state, read through libbluray.

Keys

No MakeMKV required

Recover AACS1 volume and disc keys, and derive AACS2 unit keys, from the disc and the drive.

Rip

Lossless remux

H.264, HEVC, VC-1, MPEG-2 with AC-3, E-AC-3, DTS, TrueHD, FLAC and PGS subtitles into MKV or MP4.

Encode

x264, x265, VideoToolbox

Software or hardware encoding, 8-bit or 10-bit, with sensible default track selection.

Author

BDMV and ISOs

One title or many, a BDMV folder or a UDF 2.50 image: newfs_udf on macOS, a portable writer elsewhere.

Menus

A real BD-J menu

An authored 1080p title menu, one row per title, with a background, arrow keys, digits and mouse.

DVD

VIDEO_TS too

List and rip DVD titles through ffmpeg's dvdvideo demuxer, keeping MPEG-2 and AC-3 or DTS.

TV

Episode splitting

Split a disc into per-episode files with SxxExx names, OP/ED detection and TMDB metadata.

Copy

1:1 clone

Clone the encrypted structure bit for bit, or export a decrypted ISO or folder when you want plain files.

Check

Verify before you burn

Walk the navigation, every PlayPL, every playlist and every clip, plus the BDJO, JAR and menu rows.

Burn

Native and guarded

hdiutil burn by default, growisofs when you name a device. Dry run first, confirmation required.

Automate

MCP and a real CLI

Every capability is a command and an MCP tool, so an assistant can drive the whole workflow.

The loop

Disc in, keepsake out.

Nothing is written until you say so. Every destructive step has a dry run, a confirmation or both.

Know what is on it

Insert the disc, read the title map, pick the main feature and look at the streams before a single byte moves.

Rip or build

Remux losslessly, encode for size, or take finished files and author a new disc with a menu and chapter marks.

Verify, then burn

Run the tree check, mount the ISO to read it back, and only then hand it to the writer after confirmation.

Authored menu

A menu that is actually there.

One generic Xlet reads the disc's own title list at runtime. No per-disc Java compilation.

The authored BD-J menu showing First Episode, Second Episode and Third Episode with the first row highlighted
authored BD-J menu, rendered by the Xlet and captured from a real JVM run

Downloads

Take a build.

Builds are mirrored to GoFile and file.kiwi. Links are refreshed weekly, because free tiers expire.

macOS (Apple Silicon)

Keepsake-Atelier-0.1.0-arm64.dmg

Source

cargo build --release

The DMG is not notarized. Open it once with right-click then Open, or run xattr -dr com.apple.quarantine "/Applications/Keepsake Atelier.app". The DMG bundles libbluray libaacs libbdplus; the CLI tarballs need brew install libbluray libaacs libbdplus. Linux ships a CLI, an AppImage and a deb; Windows ships a CLI zip and an NSIS installer. Both desktop builds are previews; see the platform matrix in the docs. Read the install guide.

Guides

Start where you are.

Short, task-shaped pages. Every one ends with the exact commands and the checks to run.

02

Rip a movie

Pick the main title, choose tracks, remux or encode, and find the file.

03

Author a disc

One title or a season, a folder or an ISO, with chapters kept.

04

Give it a menu

Turn on the BD-J menu, choose a background, and verify the rows.

05

Keys and AACS

KEYDB, native recovery, LibreDrive limits and what to do when it fails.

06

Burn and verify

Size query, dry run, the real write, and the read-back check.

07

DVD-Video

List the titles and copy MPEG-2 with AC-3 or DTS.

08

TV and anime

Episode split, naming, openings and endings, and TMDB.

Support

Keep the workshop open.

The app is MIT and stays free. If it saved you a weekend, there are three ways to help.

Join the Discord

Disc rips that will not start, a drive that will not unlock, a menu that needs a second pair of eyes. Bring the log.

discord.gg/SUaUrVGj5f

Buy a coffee

One-off support through Ko-fi. No subscription, no tiers, no locked features.

ko-fi.com/ghosty99

Send ETH

Ethereum mainnet. Copy the address or scan it in any wallet.

0xbBef115aD853236a350EaF04777a2AdB2e7c0317

Questions

The short answers.

Does it need MakeMKV?

No. Native AACS key recovery reads the volume ID from the drive and derives the key from the disc's MKB. MakeMKV dumps are supported as a fallback but are not required.

Why does native key recovery fail on my drive?

The volume ID needs a LibreDrive vendor read. Stock firmware on many drives does not provide it. libaacs with a KEYDB entry still decrypts, and the app says which path it used.

Are the authored menus verified?

The BDJO, the JAR and the menu rows are checked, and the Xlet is run in a real JVM harness. Hardware playback is still untested, so menus are opt-in with author --menu.

Can it burn?

Yes. macOS uses hdiutil burn, Linux uses growisofs, and Windows uses the built-in IMAPI2 stack. Dry run is the default and a write needs an explicit confirmation. A blank BD-RE or BD-R is required. The Windows write path is implemented but has not been run on a physical writer yet.

Where are keys and settings stored?

Under ~/Library/Application Support/keepsake-atelier. The KEYDB file stays local and is never uploaded.

Is there a Windows or Linux build?

Yes. Linux ships a tested CLI plus AppImage and deb builds; Windows ships a CLI zip and an NSIS installer. Both desktop builds are previews, and drive discovery, ripping and authoring work there. Burning and native AACS recovery remain macOS features.