Submitting Assignments as PDF — Formatting That Professors Accept
Professors reject assignments for wrong fonts, broken links, and mystery margins. Format PDF submissions that open correctly, print cleanly, and survive LMS upload limits.
The syllabus said "PDF only, 1-inch margins, Times New Roman 12." The submission was PDF — exported from Google Docs with Calibri, clickable links that broke offline, and a filename final_FINAL2.pdf.
The TA docked formatting points before reading paragraph one.
Assignment PDFs aren't about looking fancy. They're about opening exactly as you intended on a grader's laptop at midnight.
Pre-export checklist
- [ ] Correct citation style (APA, MLA, Chicago) applied in source doc
- [ ] Page numbers on every page except cover if required
- [ ] Fonts embedded or standard PDF fonts used
- [ ] Images at 150–200 DPI — not phone photos at full res
- [ ] Hyperlinks work or removed if rubric says print-only
- [ ] Name and student ID in header/footer per instructions
- [ ] Filename matches syllabus pattern
Word / Docs → PDF export
Use Word to PDF or native Export → PDF:
- Embed fonts — Embedding Fonts Word to PDF
- Print layout not web layout
- Disable "Document structure tags" only if file size critical and accessibility not required
Multilingual PDF Fonts if writing in multiple scripts — test characters render.
Margins and page numbers
Printable PDF Margins — home printers and PDF viewers differ slightly; 1-inch academic standard has headroom.
Legal-style numbering rarely needed — unlike Legal PDF Page Numbering — but consistent Arabic numerals help TAs reference feedback.
File size and LMS limits
Canvas, Moodle, Blackboard often cap 20–50 MB. Large image inserts blow limits:
- Compress images before placing in document
- Compress PDF after export — When Should You Compress a PDF
- Never submit unmerged 40-page scan per page — Merge PDF into one file
Email Attachment Limits apply when emailing professors directly.
Flat vs fillable
Submit flat PDFs — not fillable forms unless template provided. Fillable vs Flat PDF.
Common rejection reasons
| Issue | Fix | | --- | --- | | Font substitution | Embed fonts | | Cut-off equations | Check print preview margins | | Portrait/landscape mix | Section breaks explicit | | Rotated scan pages | Rotate PDF before merge | | Password protected | Remove protection | | Corrupt file | Re-export; don't rename .doc to .pdf |
Scanned handwritten work
Photos of notebook pages → JPG to PDF. Crop margins in Crop Image first. Ensure legibility — graders won't enhance blurry shots.
Accessibility bonus points
Tagged PDF helps disability services — PDF Accessibility Basics. Some universities require it for capstone projects.
One-page myth for resumes attached
If attaching CV with assignment, One-Page Resume PDF Myth — separate rules from essay body.
Limitations
Common mistakes
Real-world examples
When to use this approach
Conclusion
Read the syllabus like a spec. Export PDF with embedded fonts, correct margins, sane filename, and tested upload size.
Professors grade content — but formatting friction starts the rubric in the wrong column. LastName_Essay2_HIST204.pdf beats final_FINAL2.pdf every time.
LMS-specific tips
Canvas — inline preview may differ from download; test downloaded file. Turnitin — generates similarity report on text PDFs; image-only PDFs may fail text extraction. Google Classroom — Drive integration accepts PDF; verify sharing permissions not "anyone with link" on submission.
Group submissions
One PDF per group with all names on cover sheet — syllabus often specifies. Merge individual sections with Merge PDF; agree order before merge to avoid authorship disputes.
Accessibility accommodations
Students with accommodations may submit alternate formats — know disability services process before rejecting non-PDF submission.
Frequently Asked Questions
Common questions answered to help you get the most from this tool.
Vertex Solutions Editorial Team
Guides and articles are produced under this collective byline — not attributed to invented individual experts. We research tool workflows, check steps against live tools where practical, and avoid fabricated personal stories, client anecdotes, or invented test results.
- Content research — Topics come from real tool workflows, common questions, and gaps in existing guides.
- Technical review — Steps, tool behavior, and examples are checked against the live tools on this site before publication when practical.
- Fact checking — Claims about formats, browser behavior, and calculator outputs are verified against documentation and tested sample inputs where practical.
- Updates — Pages may be revised when tools, official guidance, or browser behavior changes. There is no fixed review calendar for every URL.
- Corrections — Report factual errors via Contact.
Full policy: Editorial Standards. Tool checks: How we verify tools.