How to stop students downloading course videos on Android
Never serve lectures as plain files, keep offline downloads encrypted inside your app and tied to the phone, and add FLAG_SECURE, root checks and forced updates. A watermark covers the camera.
On this page 8 sections
To stop students downloading course videos on Android, never serve a lecture as a plain video file, and play it only inside your own app. Keep any offline downloads encrypted in the app's private storage, tied to that phone and set to expire. Then add app-level controls: block screen capture with FLAG_SECURE, check for rooted phones, emulators and modified copies of your app, and force updates. No setting stops a second phone filming the screen, so a visible watermark has to cover that route.
How lectures leave an Android phone
Most Android leaks use ordinary gaps rather than clever hacks. These are the main routes, described at a conceptual level:
| Route | What it looks like | What closes it |
|---|---|---|
| Plain video links | A lecture plays from a direct file address, which opens in Chrome or a download app | Lectures never served as files, and nothing that plays outside a signed-in session |
| Downloads saved as normal files | An offline lecture appears in the gallery or Files app, ready to share on WhatsApp | Downloads kept encrypted inside the app |
| Files on an SD card | Downloads stored on a removable card that can be read in another device | Encrypted files that play only in your app, on that phone |
| Rooted phones | Other software can reach the app's private files and switch off protections | Root detection, and stricter download rules on those phones |
| Emulators | The app runs inside a computer, which can record its window | Emulator detection |
| Modified copies of the app | An altered copy of your app, passed around as an APK file with protections removed | Checks that the app is genuine, and forced updates |
| Screen recording | The phone's built-in recorder captures the lecture | FLAG_SECURE on every screen that shows content |
| A second phone | The screen is filmed | Nothing blocks it; a watermark traces it |
The last row is why no app can honestly promise "no downloads, ever". The rest can be closed, or narrowed a long way.
Why the website and web-view apps are the weak spot
If students can open the same lectures in Chrome on their phone, your app's protections don't apply there. A mobile browser can't block recording, and some Android browsers support download tools and extensions. Our guide to preventing video downloads from a website covers that side in detail.
Watch for apps that are really a website in a wrapper. Some course apps simply load the institute's website inside an app frame. They look like apps, but their videos travel the same way as on the website, and they may not use Android's protections at all. Ask your developer whether lectures play in a native player, and whether any address from the app works in a browser.
Offline downloads without the risk
Offline viewing matters to Indian students. Hostel Wi-Fi drops in the evening, mobile data runs out, and long journeys home are study time. Turning downloads off pushes some students towards pirated copies that do play offline, so the goal is safe downloads, not none.
Android helps here. Its storage documentation says other apps can't access an app's internal storage, and that on Android 10 and later those locations are encrypted. Shared folders such as Downloads or Movies are different: the gallery, file managers and WhatsApp's attach button can all see what's saved there.
A safe offline download has six properties:
- Private: stored inside the app's own storage, never in a shared folder.
- Encrypted, so the file is useless if it is copied off the phone.
- Bound: playable only in your app, on the phone that downloaded it.
- Expiring, and renewed only when the app reconnects and the enrolment is still active.
- Counted, so one account can't hold an entire course on several phones.
- Revocable: locked when a student's access ends.
If downloads go to an SD card to save space, the same rules apply. A card can be taken out and read elsewhere, so encryption carries all the weight.
App-level controls on Android
| Control | What it covers | Its limit |
|---|---|---|
| FLAG_SECURE | Screenshots, screen recordings and screen sharing show black | Can't see a camera; weaker on rooted phones and modified apps |
| Root and emulator checks | Spot phones and set-ups where protections can be switched off | An arms race, so the checks need regular updates |
| Genuine-app checks | Google's Play Integrity API lets an app check it is the unmodified version from Google Play, on a genuine, certified device | Google says not to use it as the only defence |
| Minimum app version | Moves students off old versions that lack protection | Needs a release process that keeps up |
| Audio capture setting | Stops other apps capturing the lecture's sound | A microphone near the speaker still hears it |
| Visible watermark | The student's identity on every frame, including offline | Can be cropped or covered; invisible marks help trace those copies |
Our explainer on Android's FLAG_SECURE setting covers what it blocks and the gaps it leaves. Our guide to root and emulator detection explains why modified phones matter so much. Google's Play Integrity overview describes the genuine-app checks.
What to do about rooted phones
Rooted phones are the hardest call. Blocking them entirely is the safest choice, but some honest students have rooted or modified phones, bought second-hand or set up by a friend. A middle path is to allow streaming but not downloads on those phones, with a clear message explaining why. Whichever you choose, decide it deliberately and tell students before they pay, rather than letting them find out on the night before a test.
Stripping these protections to copy lectures is not a grey area. In India, circumventing an effective technological measure with the intention of infringing copyright is an offence under section 65A of the Copyright Act, 1957. This is general information, not legal advice.
Gaps institutes leave open
- Old APK files, from before protection was added, still shared in WhatsApp groups.
- Free and demo lectures hosted elsewhere, such as unlisted video links, that turn out to include paid content.
- PDFs and solutions that open in another app instead of inside your own.
- Staff and teacher apps with download buttons, or admin panels that export original files.
- Previews and thumbnails that show content outside the protected player.
- A second, older app under a different name, still connected to the same videos.
Each of these is a door that bypasses the protected player entirely. One open door undoes the rest.
Test your own Android app in an hour
You don't need technical skills for this. Use an ordinary student account and two Android phones from different brands, one older and one recent:
- Download a lecture, then open the gallery and the Files app. Nothing playable should appear.
- Try attaching a file in WhatsApp. There should be no lecture to pick.
- Take a screenshot and use the built-in screen recorder on the player, PDFs and tests. Each should be black or blocked; play the recording back to check the audio.
- Copy any share link from the app and open it in Chrome while signed out. It shouldn't play.
- Keep a phone offline past the download's expiry. The lecture should stop until the app reconnects.
- End the test account's enrolment, then reconnect. Downloads should lock.
- Film a minute of a lecture with the second phone. The student's identity should be readable.
If any test fails, ask your developer or platform for a fix and a date. For the wider picture of building or buying a course app, see how to create your own coaching app.
Upclass gives institutes branded apps in their own name on Android, iOS, Windows and Mac. VidSafe adds VidSafe proprietary encryption, screen- and camera-recording detection, RASP, account-sharing prevention, PDF watermarking and dynamic watermarking. VidSafe adds visible and invisible watermarks that are extremely hard to remove, even after heavy re-encoding, so a leaked copy can be traced back to the account it came from. See our LMS for coaching institutes.
Frequently asked questions
Can you stop screen recording on Android?
Mostly, for standard tools. An app can use Android's FLAG_SECURE setting so screenshots and screen recordings of its screens come out black. It can't stop a second phone filming the screen, and rooted phones, emulators and modified copies of the app can undermine it.
Where are downloaded course videos stored on Android?
It depends on the app. A well-built course app keeps downloads encrypted in its own private storage, where other apps can't reach them and the gallery can't see them. Weaker apps save normal video files to shared folders, where any file manager or messaging app can pick them up. Check your gallery after downloading a lecture to see which kind you have.
Should I turn off offline downloads to stop piracy?
Usually not. Students on patchy networks rely on them, and removing them can push some towards pirated copies. Offer downloads that are encrypted, playable only in your app on that phone, limited in number and set to expire when access ends.
Can students download videos from an app that blocks screenshots?
Possibly, because blocking screenshots doesn't decide how videos are delivered or stored. If the app plays lectures from plain file links, or saves downloads as normal files, they can leave the phone without any recording at all. Blocking capture and protecting delivery are separate jobs, and an app needs both.
