Students: blur a screenshot for class without leaking classmates
Group chats and LMS pages in homework. Cover names and emails before you upload.

The assignment says “screenshot the group discussion.” The group discussion has twelve classmates’ emails.
School work travels: LMS dropboxes, shared folders, a parent printing the PDF, a teacher recycling the slide next year. None of those places asked for a roster. Cover names you do not have permission to publish. Teachers who reuse slides should do the same. Proof you posted still owes the rest of the group a barred frame.
Use opaque bars on emails, student IDs, grades, home addresses in a parent thread, and faces in a Meet grid if the brief did not require faces. Crop when the extra tiles are irrelevant. Do not install a random APK “editor” on a school profile to smear pixels that a browser tab can cover.
What the rubric is actually grading
Most screenshot assignments check that you used the tool, posted on time, or captured a UI state. They are not asking you to publish the study group. If the prompt is “show your formula in Sheets,” crop to the cells. If it is “show you replied,” bar every other student’s address and any instructor comment that was not meant for a portfolio.
Group chats on Discord or WhatsApp are worse than LMS forums because nicknames, phone numbers, and a parent’s contact sit in the same screenshot. A PTA thread you were told to “just send” is still other people’s numbers. Bar or crop. If you need to prove a message existed, keep the timestamp and the relevant sentence, not the member list.
What counts as someone else’s data
- Classmate emails, usernames, and student ID numbers
- Faces and real names in a Meet or Zoom grid
- Grades, comments, and accommodation notes in the LMS rail
- A parent’s phone, address, or workplace in a forwarded chat
- Your own ID or lunch-account number if the file will be public
Your own name on a homework header can stay if the LMS already requires it. Your passport photo in a “upload ID for the field trip” thread should not be screenshotted into a group chat. Black-bar ID numbers and addresses even when the photo is of you. Portfolios and scholarship blogs get scraped.
Teachers and recycled decks
A slide that shows last year’s discussion as an exemplar still shows last year’s students. Re-bar or recrop before this year’s upload. Do not rely on a yellow highlight over a name. Do not leave the gradebook in a “how to submit” video. For an example thread, use fake names or bar every real identifier until only UI chrome remains.
Shared Chromebooks keep downloads. Export the barred PNG, submit that, delete the raw capture from Downloads and from the camera roll if you used a phone. Photos of the screen add location metadata and other students in the room.
Should I bar my own email on a school screenshot?
If the file stays inside the assignment dropbox, your school email is usually expected. If you will post the same PNG on a public GitHub gist, a Discord help channel, or a college application portal that becomes a brochure, bar the address. The rule is destination, not vanity. Assume a “private” class Discord is not private.
FAQ: the professor asked for the whole window
Whole window still allows bars. Cover the roster, the mail chip, and the notification that named another student. If they truly need unredacted PII, they should collect it through the LMS, not through a PNG in a discussion board that the whole class can download.
FAQ: can I blur faces in a group Meet instead of bars?
Faces are the one case where a strong blur is sometimes enough for “not recognizable in a hallway.” Names, emails, IDs, grades, and addresses are not that case. Use black rectangles on text. If a classmate did not consent to be in the homework PDF, crop them out or bar the tile. Name labels are in the meeting guide linked below.
FAQ: what about code screenshots with a classmate’s repo path?
Paths contain usernames. Error dumps contain emails. Cover those strings the same way you would in a job application. Keep the compiler error. If the assignment is pair programming, you still do not need their home folder in the PNG you upload to a public gist “for help.”
Chromebook capture quirks: Chromebook screenshots. Grid calls and name labels: Meet and Zoom. For the LMS upload, cover the roster in the tab so you are not shopping for an editor on a managed device.
