Free · no signup to try · nothing to install

Disk Forensics Lab

Students can tell you that deleted files are not really gone, and still believe an investigator switches on the suspect's laptop and looks around. Real examiners never do that. They work on a copy, prove the copy matches with a hash, and read what the disk holds rather than what the desktop shows. Disk Forensics Lab hands students the copies of a laptop and a USB stick from a school trophy theft and lets them do that work, from the hash check to the written report.

This is the whole app, opening on the evidence bench. Press Verify the image on each item, then open Examine. The case is made up and different every time it opens, so whose laptop it is changes. Saving needs a free account.

Open it full screen

Using this with a class? Make a free class and add your students yourself: each gets a username and password, with no email or Google account needed. Or give them one join code. Using Google Classroom? Post the link there; with a free class, the link also puts each student in your class, so you see their work. mytekDev is also available from the Google Workspace Marketplace, so your school's Google admin can install it for everyone.A first lesson: Open Examine on the laptop, click chores.txt in Documents and put the Picture or text tab on the projector. Ask the class what kind of file it is. It opens as gibberish, because its name says text. Then open the Bytes tab and read the first three bytes together, FF D8 FF, the signature of a JPEG photo.

Set up a free class Share to Google Classroom
Put this on your class site

Students can use Disk Forensics Lab right on your page, with no account. What they make stays on that page; to keep their work, they make a free account.

Google Sites: Insert, then Embed, then By URL, and paste this address.

https://mytekdev.com/try/diskforensicslab?embed=1

Canvas, a blog, or any page that takes HTML: paste this code where you edit the page as HTML.

<iframe src="https://mytekdev.com/try/diskforensicslab?embed=1" width="100%" height="640" style="border:0" allow="fullscreen" title="Disk Forensics Lab demo from mytekDev"></iframe>

What a student actually does

The case is Crime Scene Lab's trophy theft from the digital side. Someone broke the school's trophy case overnight and took the cup. One keyholder's laptop and the USB stick from their bag were taken with their consent, imaged, and handed to the student, with a chain of custody card for each that names who handed it to whom and when. The first job is on the evidence bench: press Verify the image, and the SHA-256 of the student's copy has to match the hash taken when the drive was imaged. Nothing can be tagged until it does.

Examine is a forensic tool's window in miniature: a folder tree, a file list with each file's type by its name beside its type by its bytes, and a pane with five tabs, Picture or text, Bytes, Photo details, Times and Hash. The laptop's Recycle Bin holds its deleted files under $R names, with $I records that say where each came from and when it was deleted. Documents holds chores.txt, which is a photo. The USB stick is a real FAT32 disk image: its deleted entries start with the byte E5 and show with their first letter lost, one deleted photo is half overwritten by a newer file, and three photos are carved out of free space with no name and no folder.

In High school mode the student earns each answer: they pick a file's type from its first bytes before the list will say it, and they turn a photo's GPS position from degrees, minutes and seconds into decimals before the town map shows the pin. Middle school mode names the types and does the conversion. Tag as evidence puts a file on the case with a note in the student's words, and Timeline lines every tagged time up in UTC, with the break-in window shaded and a close-up of that night. Each time says where it came from, NTFS in UTC, FAT and the camera's clock in local time with no zone, so the student sees why examiners convert.

Start a copy in a virtual machine opens the laptop the way its owner saw it, on a desktop in our own style: chores.txt opens in Notepad as gibberish, the Recycle Bin shows friendly names, and the USB stick shows no deleted file at all. Turn on the original laptop is there too, as the mistake an examiner never makes; it changes the original's hash, and the report says so. The Report gathers the evidence, the hashes, the tagged files and the timeline, and the student writes the findings, makes the call, and says what the evidence cannot say. Hand in checks it the way a teacher would, including that nothing says "proves" or "guilty".

The USB stick open in the examiner's window, with _ROPHY.JPG in red and marked DELETED. Its Photo details: a picture of a gold cup on a car's back seat at night, camera Kestrel X2, camera time 2026:10:16 00:47 with no time zone, GPS time 05:47 UTC, latitude 37 degrees 9 minutes 54.67 seconds north, longitude 101 degrees 47 minutes 2.75 seconds west, GPS error about 4.9 meters. Beside it, a drawn town map with a red pin and a dashed circle at the pull-off on Old Quarry Road, away from the school.

The photo deleted from the USB stick, recovered. Its EXIF gives the phone, the camera's clock with no time zone, the GPS clock in UTC and the position, which lands on the town map at the quarry road. The same bytes, hash for hash, are in the laptop's Recycle Bin.

What they are learning while they work

Nothing here is presented as a lesson. This is what the activity is made of.

What the student doesWhat it is
Presses Verify the image and watches the two SHA-256 values match Hashing and integrity. A hash is a fingerprint of every bit. Examiners hash the drive when they image it and again before they work, so they can show the copy is exactly what was seized. A matching hash says two files hold the same data, not who made them.
Opens chores.txt and reads FF D8 FF in its first bytes File signatures. Most file types start with the same few bytes. Windows picks a program by the name's ending, so renaming a file changes what opens it, not what it is. A mismatch is a lead to check, not a finding.
Finds _ROPHY.JPG on the stick, first letter gone, and recovers it Deleted is not gone. On a FAT stick, deleting a file marks its entry with the byte E5 and frees its space. The data stays until something new is written over it, which is why one photo comes back whole and another only down to the part a newer file took.
Reads the laptop's Recycle Bin and the card about its SSD When deleted really is gone. On a modern laptop's SSD, a file deleted for good is usually wiped by the drive soon after (TRIM). Students learn both halves: what survives on a USB stick, and why the same trick fails on the laptop.
Converts 37 degrees 9 minutes 54.67 seconds north to decimals and sees the pin land Metadata and EXIF. A phone writes the camera, the time and often the position into each photo. The camera's time has no time zone; the GPS time is in UTC. The position is good to a few meters under open sky, a circle, not a spot.
Puts tagged files on the timeline and sees the camera time and the GPS time land together Timelines and time zones. NTFS keeps times in UTC, FAT and the camera keep local time. A copied file's created time is after its modified time, which is what a copy looks like, not tampering.
Writes "consistent with" instead of "proves" and lists what the evidence cannot say Reporting. Examiners report what is on the media. Who held the phone, or who took the cup, is for investigators and courts. The report check holds students to that.

How to tell whether it landed

Ask, and let them show you. A student who has understood it can answer these without help.

Use it in your subject

Not a technology class? Then the app is how students show what they learned in your unit. More projects for every subject.

High school cybersecurity and CTE digital forensics

Addresses Utah CTE Cyber Forensics (analyzing forensic images, hashing for integrity, metadata, chain of custody, a timeline in the report), Texas's Digital Forensics course on collecting and examining data while preserving its integrity, and the NICE Framework's Digital Forensics work role tasks: file signature analysis, timeline analysis, recovering information from forensic data sources, processing forensic images.

Cisco CCST Cybersecurity and AP Cybersecurity

CCST Cybersecurity's "Explain digital forensics and attack attribution processes": identify, document, preserve and secure evidence, and keep the chain of custody. AP Cybersecurity 5.6.D, identifying whether a file has been altered by verifying its hash.

Cyber competitions

The Competition (NCL style) level asks eight questions with one exact answer each, read from each student's own case: a SHA-256, a latitude to four places, a Recycle Bin path, a file size, a phone's offset from UTC. NCL's Forensics category is open to high school students; CyberPatriot's images open with Forensics Questions, and its middle school division can start in Middle school mode.

Forensic science electives

The second half of Crime Scene Lab's trophy case, for classes that have walked the scene. No coding needed.

Practical notes

For co-ops, microschools, and classrooms

Each project is its own case, so students side by side have different answers and the work cannot be copied. With a free account the work is saved as a project, tags, notes and report included, and a teacher who wants one case for the whole class sets it in Setup and shares that project for students to start from.

Common questions

Is it free?

Yes. Disk Forensics Lab has no paid tier, and it can be tried right on this page without an account. Saving needs a free account.

Is the evidence real?

The case is made up and so are its people, but the USB stick is a real FAT32 disk image, written byte for byte. Sleuth Kit, the engine under Autopsy, lists the same files and deleted entries and recovers the same bytes as the app, and exiftool reads the same photo details. The laptop is a model of a Windows laptop with real file contents and real Recycle Bin records, not a whole drive image.

Does it read anything on the student's computer?

No. It never touches the computer's own drives or files. Everything is built in the page from the case.

Why are deleted files found on the USB stick and not the laptop?

Because that is what a modern laptop does. On an SSD, a file deleted for good is usually wiped by the drive soon after, so the laptop gives back only its Recycle Bin. A USB stick usually keeps deleted data until it is written over. The app says so where it matters.

What does it simplify?

One case, two items. The laptop is a model rather than a byte-for-byte image, so its hash is worked out from the model. There is no memory, phone, browser history, registry or event log in this version. Recovery follows Sleuth Kit's rule for deleted FAT files, and carving looks only for JPEG photos. The map's coordinates are real and fall on open grassland in Kansas; the town on it is made up.

Does it teach students to hide evidence?

No. Renamed files, deleted files and switched-on laptops appear only as things an examiner finds or a mistake an examiner avoids. The app's words are an examiner's: findings are "consistent with", never "proves".

Where do the facts come from?

NIST SP 800-86 and SWGDE for the evidence process, Microsoft's documentation for file times, the Exif standard and ExifTool's tag tables for photo details, Sleuth Kit's own source for recovery, and studies of SSD TRIM by Bell and Boddington and by King and Vidas. An independent review checked every card against them.

Still have a question? Ask us, and a person will write back.

Where to go next

Start with Disk Forensics Lab

Trying it costs nothing and takes about five minutes. An account is what makes the work last.

Disk Forensics Lab is one of the making apps on the platform. The USB stick's bytes, the photos' details and the hashes are all real and checked against forensic tools; the case and its people are made up.
Page last reviewed November 2026.
Google, Google Classroom and Chromebook are trademarks of Google LLC.