Quick answer: use Blu-ray copy software when you want another disc, an ISO image, or a Blu-ray folder. Use a Blu-ray ripper when you want one or more normal video files such as MKV or MP4. If you want both a complete archive and a Plex library, keep an ISO or folder as the archive and create a separate MKV for playback.
Choose in 60 seconds
| Your actual goal | Use this workflow | Best starting output | Keeps the original disc menu? | Blu-ray writer required? |
|---|---|---|---|---|
| Make another physical Blu-ray | Copy | Blank disc, preferably from a verified ISO master | Yes in full-disc mode | Yes |
| Keep a complete hard-drive archive | Copy | ISO or Blu-ray folder | Yes in full-disc mode | No |
| Add a movie to Plex or Jellyfin | Ripper or lossless remux | MKV | No | No |
| Make a smaller file for TVs, phones, or tablets | Ripper and encoder | MP4, usually H.264 or H.265 | No | No |
| Preserve everything and also use a media server | Both | ISO or folder plus MKV | In the archive only | No, unless writing a disc |
The fastest way to avoid buying the wrong tool is to decide whether you need a disc-shaped result or a title-shaped result.
- A disc-shaped result keeps the Blu-ray structure and can include menus, extras, and multiple titles.
- A title-shaped result keeps the movie or episode you selected in a normal media container that apps can index and play.
What Blu-ray copy software does
Blu-ray copy software generally reads a disc, ISO, or Blu-ray folder and produces another disc-style destination. Current product documentation from DVDFab Blu-ray Copy distinguishes blank-disc, ISO, and folder output from its ripper’s MP4 and MKV output.
Choose copy software when one or more of these statements is true:
- You want to keep the original navigation and menu experience.
- You want the extras and disc structure, not only the main movie.
- You want a single ISO master that can be stored, mounted, or written later.
- You want to write authorized material to compatible blank Blu-ray media.
- You do not yet know which titles, audio tracks, or subtitles you will need later.
ISO or Blu-ray folder?
An ISO is one archive file containing the disc image. It is easier to name, move, checksum, and store as one unit. A Blu-ray folder exposes the disc’s file structure directly, which is useful when another program needs those files but is less convenient to move or verify.
For an ordinary Blu-ray, plan around the physical format’s capacity: the Blu-ray Disc Association lists 25 GB for single-layer discs and 50 GB for dual-layer discs. The actual occupied space may be lower, but the destination must still have enough free space for the job and temporary files.
What a Blu-ray ripper does
A Blu-ray ripper generally selects one or more titles and outputs normal video or audio files. Current DVDFab Blu-ray Ripper documentation lists formats such as MP4, MKV, M2TS, and audio files, which illustrates the practical difference from disc, ISO, and folder copying.
Choose a ripper when one or more of these statements is true:
- You want a movie or episode as a file in Plex or Jellyfin.
- You want to remove unneeded languages, commentary tracks, or extras from the playback copy.
- You want a smaller file for a phone, tablet, laptop, or smart TV.
- You need a container and codec combination supported by a specific client device.
- You care more about fast access to the main title than the original disc menu.
MKV does not automatically mean compressed
MKV is a container, not a quality setting. MakeMKV’s format documentation explains that an MKV can hold multiple video, audio, subtitle, chapter, and metadata streams. A lossless remux can place the selected streams into MKV without re-encoding the video.
This is usually the safest first result for a media-server workflow: create and verify the MKV before deciding whether a smaller encoded copy is necessary.
MP4 does not automatically mean low quality
MP4 is also a container. Quality and size depend on the video codec, audio codec, bitrate or quality target, runtime, and encoder settings. HandBrake’s current container documentation lists H.264 and H.265 support for both MP4 and MKV, while noting differences in supported audio and subtitle combinations.
MP4 is usually the better starting point when broad client compatibility matters more than keeping every original stream. Encode a short chapter first; do not wait for a full movie to finish before discovering that the target device cannot play the selected audio or subtitle format.
Workflow A: keep a complete hard-drive archive
- Confirm that the drive can read the exact disc type and that the destination has enough free space.
- Choose full-disc ISO or folder output when menus and extras matter.
- Save the output to a temporary working location with additional free space available.
- Open the result in a compatible player and check the main title, one extra, several chapter jumps, required audio tracks, and required subtitles.
- Record the software version, drive model, elapsed time, output size, and any warnings.
- Create a checksum and keep a second copy on another storage device before treating it as an archive.
Use a reader for this workflow. A Blu-ray writer is only needed if the final destination is another physical disc.
Workflow B: build a Plex or Jellyfin library
- Create a lossless MKV of the correct movie or episode before considering compression.
- Keep only the audio and subtitle tracks you expect to use, but preserve forced subtitles when they are needed for parts of the film.
- Test the file on the weakest or most restrictive playback client in your home, not only on the server computer.
- Confirm whether playback is Direct Play, remuxed, or transcoded and note which audio or subtitle choice changes that result.
- Name and organize the file before importing a large batch.
Plex’s current naming guide recommends a movie folder and filename in the form MovieName (year)/MovieName (year).ext. It supports both MKV and MP4 examples. Jellyfin also supports common containers, but its client codec table shows why the same file may Direct Play on one device and require remuxing or transcoding on another.
Original Blu-ray menus are not the organizing model for Plex or Jellyfin. If the menus and extras matter, keep a separate ISO or folder archive instead of trying to make one file serve both purposes.
Workflow C: create a smaller MP4
- Start from a verified title rather than troubleshooting title selection and encoding at the same time.
- Choose a preset for the actual target device. H.264 with compatible audio is the conservative choice for broad playback; H.265 can reduce storage needs but requires newer client support.
- Encode a representative chapter containing motion, dark scenes, subtitles, and surround audio.
- Compare the sample with the source on the target screen and audio system.
- Check subtitle behavior, chapter navigation, lip sync, aspect ratio, and audio channels.
- Encode the complete title only after the sample passes.
Keep the verified source or lossless archive. A smaller playback copy should not become the only remaining source unless that tradeoff is intentional.
What each result normally preserves
| Feature | Full-disc ISO/folder | Lossless MKV | Encoded MP4 |
|---|---|---|---|
| Original disc menu | Usually yes | No | No |
| Main movie | Yes | Yes, when selected correctly | Yes, when selected correctly |
| Extras | Yes in full-disc mode | Only selected extras | Only separately encoded extras |
| Chapters | Disc structure | Usually supported | Supported by compatible workflows |
| Multiple audio tracks | Yes | Yes, when selected | Possible, but compatibility varies |
| Multiple subtitles | Yes | Yes, when selected | Possible, with more format limitations |
| Original video stream | Yes in a lossless copy | Yes in a lossless remux | Usually re-encoded |
| Small file size | No | Usually no | Yes, depending on settings |
| Easy Plex/Jellyfin indexing | No | Yes | Yes |
“Supported” is not the same as “verified.” The exact application version, profile, and playback client still need testing.
Common wrong choices
Buying copy software for Plex
An ISO may be an excellent archive but a poor everyday Plex library file. If the goal is clicking a poster and immediately playing the main title, start with MKV.
Encoding before checking the title
TV discs can contain many similar playlists. Verify episode order, runtime, language, and opening scene before starting a batch encode.
Assuming a writer is always required
A reader is enough for ISO, folder, MKV, and MP4 destinations. Paying extra for a writer only helps when you intend to write blank media.
Assuming the container guarantees playback
An .mkv or .mp4 extension does not tell you whether the client supports the video codec, audio codec, subtitle format, HDR profile, or channel layout inside it.
Treating a completed progress bar as verification
A job can finish while still containing the wrong title, missing forced subtitles, an unwanted commentary track, or a file that triggers unexpected transcoding. Verification is a separate step.
Record this evidence for every real test
Use the same fields every time so results from different drives and software versions can be compared:
| Field | What to record |
|---|---|
| Test ID | A private label that does not expose unnecessary personal media details |
| Source | Blu-ray or 4K UHD, layer/capacity when known, movie or episodic structure |
| Drive | Exact model and firmware version |
| Computer | Operating system, CPU, GPU, memory, and connection type |
| Software | Product, exact version, module, and output profile |
| Result | ISO, folder, MKV, or MP4 plus codec details |
| Performance | Load time, processing time, average speed, and output size |
| Reliability | Warnings, read retries, failed jobs, and whether a retry changed the result |
| Preservation | Menu, chapters, audio tracks, subtitles, forced subtitles, and extras |
| Playback | Player or client, Direct Play/remux/transcode status, visible or audible problems |
| Integrity | Checksum, second-copy status, and verification date |
This test record is the beginning of CopyBluray’s defensible evidence layer. Product claims should remain labeled as vendor claims until the same scenario has been reproduced on a recorded test setup.
Frequently asked questions
Is copying the same as ripping?
Not in practical software terminology. Copy tools normally produce another disc-style destination such as a disc, ISO, or folder. Rippers normally produce title-based video or audio files such as MKV or MP4.
Is MKV better than ISO?
They solve different jobs. ISO is better for keeping the complete disc as one archive file. MKV is better for selecting a title and using it in a media library.
Is MKV better than MP4?
MKV is more flexible for multiple audio and subtitle formats. MP4 is often easier to play across a broad range of devices. The codecs and tracks inside the container matter as much as the extension.
Do I need both copy and ripper software?
Only if you need both a complete disc archive and a separate playback file, or if one product does not cover both workflows. Decide on the outputs first, then check whether one tool already creates them.
How much storage should I reserve?
For lossless ordinary Blu-ray archives, plan around 25–50 GB per disc plus temporary working space. Compressed files vary widely, so test one representative title before estimating an entire collection.
Sources checked for this edition
- Blu-ray Disc Association: disc capacity
- DVDFab Blu-ray Copy: current copy outputs and modes
- DVDFab Blu-ray Ripper: current file outputs
- MakeMKV: MKV container capabilities
- HandBrake: MKV and MP4 container support
- Plex: movie naming and organization
- Jellyfin: client codec and container support
Sources were checked on July 12, 2026. The next required review is October 12, 2026. Hands-on speed, output-size, failure-rate, menu, subtitle, and audio verification has not started and is not implied by this guide.