Email was not designed for collecting 30 files from 30 people. Ask a class to email their homework and you get thirty separate threads, half the attachments named "homework.docx", two files in your spam folder, and no way to see at a glance who has not submitted. This guide covers the setup that replaces that - for teachers, lecturers and tutors - and the small habits that make the difference between a tidy ZIP and an evening of forensic file matching.
If your school gives you an LMS, use it
Google Classroom, Moodle, Canvas and their peers exist precisely for assignment collection, and they tie submissions to rosters and grading. If your institution provides one, stop reading and use it.
A standalone upload page earns its place in the gaps: your school has no LMS (common for tutors, music schools, community courses), the LMS rejects the files you need (video projects, large design files), you teach across institutions and want one collection point, or the submitters are not enrolled students at all - parents sending photos of younger kids' work, guest workshop participants, applicants to a program.
One page per assignment, not one per class
The tempting setup is a single evergreen "submit here" page for the whole course. It works, but everything lands in one pile and you sort by hand. A page per assignment - "Biology 2B - Lab 3 (due Oct 12)" - costs a minute to create and gives you a clean per-assignment ZIP with nothing to sort.
Set the page expiration to the assignment deadline (pages run up to 10 days ahead - extend for longer projects). The page stops accepting files when the deadline passes - the deadline enforces itself, and "the link stopped working" is a conversation you have once, not a policy you police.
Naming conventions matter more than you think
A class of 30 each submitting 4-6 files produces 120-180 items in the ZIP. Without a naming rule you get "Lab3.pdf", "lab report final.docx", "asdf.pdf" - and matching files to students means opening each one.
Put the exact filename pattern in the page description and hold the line: LastName_FirstName_Lab3.pdf. Students follow a concrete example far more reliably than an abstract rule. If your tool records the uploader's name per file, the convention is your backup rather than your only hope - but it still saves you when files get forwarded or re-uploaded.
Catch wrong files before grading night
A predictable fraction of every class submits the wrong thing: a blank document, last semester's essay, a screenshot of the instructions instead of the report. These surface in the dashboard if you look for two signals - files suspiciously small for the assignment (a full lab report under 50 KB is not a lab report), and the wrong type entirely (an image where you expected a PDF). Two minutes scanning file sizes before the deadline turns "half the class resubmits after grading started" into a couple of quiet nudges.
Restricting the page to the file types you expect ("documents only" for essays) removes most of this class of error before it happens - and blocks the executable nobody should be sending you anyway.
Subject-specific notes
- Essays and papers: documents only, one file each. The simplest case - the naming convention does all the work.
- Lab reports and projects: multiple files per student is normal (report + data + photos). Ask students to bundle their own work into one ZIP before uploading; 30 ZIPs beat 160 loose files. One catch: ZIP is not part of the "documents only" preset - if you ask for bundles, leave the file types unrestricted.
- Art, design, media: files are big - scans and video easily hit per-file caps (200 MB on getfiles.app). Tell students the cap and the accepted formats up front, and expect phone-camera uploads of physical work.
- Thesis and long drafts: submissions repeat over weeks. Keep one page per milestone rather than one per document, and the version history sorts itself chronologically in the dashboard.
Tutors: smaller scale, different shape
Private tutors collect from five students, not thirty, but continuously - every week, often as phone photos of handwritten pages. Two adjustments: keep one long-lived page per student (their whole history in one place beats a weekly link hunt), and expect parents to be the ones uploading for younger kids, which is exactly why a no-account upload page beats "install this app" - the friction has to be near zero for someone doing you a favor on their phone.
Email vs upload page, honestly
| Upload page | ||
|---|---|---|
| Files in one place | 30 threads | one dashboard |
| See who submitted | scan inbox | one list |
| Download everything | one by one | single ZIP |
| Size limit | ~25 MB | up to 200 MB per file |
| Student friction | write mail, attach | open link, drop file |
| Wrong-file detection | open each mail | scan sizes/types in dashboard |
Email keeps one honest advantage: for 3-5 students it is fine, and everyone already has it. The crossover comes with a full class, where per-submission overhead multiplies by thirty.
Student work is personal data
Names attached to graded work, sometimes photos of minors' handwriting - treat the collection point accordingly. Let pages expire after the assignment closes, download what you need for your records, and do not keep a public URL accumulating a semester of student files. An expiring page makes cleanup automatic, which is the only kind of cleanup that reliably happens.
If you teach minors, check what your school or jurisdiction says about third-party tools before routing student work through any external service - including this one. "The teacher liked it" is not a data-processing agreement.
If you need a collection point like the one described here, getfiles.app does upload pages with deadlines, file-type restrictions, per-file uploader names and one-ZIP download, free, with no accounts required from students or parents.