Merge PDF files on a school Chromebook without uploading sensitive student records

You can merge PDF files on a school Chromebook without uploading sensitive student records by keeping every step local — converting documents to PDF inside Chrome or Google Docs, combining them with an offline tool such as pdfunite in the built-in Linux container, and reserving any cloud-based tool for files that contain no student personally identifiable information. The merge itself is the easy part; the real work is deciding which file you are allowed to put into which tool.

The Challenge

A special education teacher has 27 scanned progress reports, one per student, and needs a single packet for each family meeting on Thursday. A school counselor has three transcripts and a scheduling form per graduating senior. A librarian needs a 12-page program folded into a booklet for parent night. All of them are sitting at a district-issued Chromebook with a locked-down extension list, no admin rights, and a Google Drive account that lives inside the district's tenancy.

The Chromebook Files app has no merge button. Browser tabs can open PDFs, but most "merge PDF" websites are built around an upload form, and that upload is exactly the action a district data-governance policy is designed to prevent. Meanwhile the deadline has not moved: the packets still need to be printed, folded, and handed to families.

So the practical question is not "what is the fastest merge tool." It is: which merge methods work entirely on the device, and which ones are acceptable only for non-sensitive documents?

Why This Matters for K-12 Educators and Student-Support Staff

• Confidentiality obligations sit with the district, not the tool. Student records — IEP and 504 documentation, grades, health notes, discipline records, counseling notes — are governed by district policy and by student-privacy rules such as FERPA. That means a tool's terms of service do not transfer your obligation; they only add a second party to the risk. Before any file with identifiable student data leaves the device, the destination needs to be a district-approved system.
• Managed Chromebooks remove the usual shortcuts. Extension installs, Android app installs, and the Linux development environment can all be switched off by admin policy. Build your workflow around what your device actually allows, and confirm the Linux container option with IT before you depend on it.
• The printing step is where packets actually fail. Merging is trivial compared to imposing pages correctly for a folded booklet. A saddle-stitched booklet folds a stack of sheets in half, so each physical sheet holds 4 logical pages, 2 on each side, and imposition is the process of reordering PDF pages so that duplex printing and folding produce the correct reading order. If the page count is not a multiple of 4, blank pages must be added to complete the last sheet. Manual page reordering has roughly a 60% success rate, and Word cannot do imposition at all — so a stack of pages that "looks right" on screen is often wrong on paper.

The Workflow

Step 1. Sort every file into two buckets before you open a tool

Bucket A: contains identifiable student data (names, ID numbers, grades, services, health information). Bucket B: contains none (blank forms, newsletters, public event programs, your own lesson materials).

Bucket A never goes to a consumer upload site. Bucket B can use whatever is fastest. Do this triage first; it determines every decision below.

Step 2. Stage the files locally

Download the source PDFs into a single folder under My files in the Files app, named for the packet (for example, 2026-03-14_family-meetings). Working from a local folder rather than a synced Drive folder keeps the files from moving around mid-task and gives you one place to delete from at the end.

Step 3. Convert anything that is not a PDF, without leaving the device

• Google Docs / Slides: File → Download → PDF Document (.pdf). The conversion happens on Google's side but the output lands directly in your local Downloads folder, and the file stays inside the district tenancy.
• Web pages or image-heavy handouts: Chrome's print dialog → Destination: Save as PDF. This produces the PDF locally on the Chromebook.
• Scanned paper: most district copiers email or save a PDF directly; keep that destination inside the district system rather than a personal account.

Step 4. Merge with a method that keeps the bytes on the device

Pick the first option your device and IT policy allow.

• Linux container (Crostini) with pdfunite. If Linux is enabled, the terminal gives you the cleanest offline merge available on a Chromebook: pdfunite part1.pdf part2.pdf part3.pdf merged.pdf. The files never touch a network. pdfunite ships with poppler-utils; Ghostscript offers the same result with gs -sDEVICE=pdfwrite -o merged.pdf part1.pdf part2.pdf.
• PDFsam Basic. Open-source merge, split, and rotate tool that runs locally. On a Chromebook it needs the Linux container (it is a Java desktop application), but it is fully offline and has no upload step.
• A self-hosted or district-hosted instance of a tool like Stirling-PDF. If your IT department runs it inside the district network, files stay inside the perimeter. This needs IT cooperation, so it is a "request it once, use it for years" option rather than a same-day fix.
• A browser tool that processes in the tab. Some PDF utilities run entirely client-side. You can verify this yourself: open the page, disconnect Wi-Fi, and try the merge. If it still works, the file never left the Chromebook. If it fails offline, it was uploading and it is Bucket B only.
• An imposition-aware tool when the output is a booklet. One option is the OctopusPDF booklet tool, which takes a PDF, reorders pages for duplex printing and folding, adds gutter margins, and returns a print-ready PDF; the free tier allows 3 conversions per day and Pro adds unlimited conversions with a full print preflight report. Use it — or any equivalent — only after confirming with your district that the specific file may leave the device.

Step 5. Verify page count, order, and blank pages

Open the merged file and check: correct number of documents, correct order, no duplicated pages, and whether the total is a multiple of 4 if the packet will be printed as a saddle-stitched booklet. A good booklet tool detects a page count that is not a multiple of 4 and adds the blank pages automatically; if you are doing it by hand, add the blanks yourself or accept a misaligned final sheet.

Step 6. Proof one sheet before running the full print job

Print a single duplexed sheet, fold it, and read the page numbers in order. This one step catches nearly every imposition error before it costs you 30 copies and a rescheduled meeting.

Step 7. Clean up

• Delete the local working folder, empty the Downloads area, and empty Trash.
• Sign out of any shared or cart-based Chromebook you used.
• If a copy had to live in Drive during the process, confirm it is in a district-approved location and delete stray duplicates.

Pre-publish checklist

• File triaged as Bucket A (student data) or Bucket B (no student data)
• Source files staged in one local folder
• Merge method verified to work offline, or the tool is district-approved
• Page count and page order confirmed on the merged file
• Booklet page count is a multiple of 4 (blanks added if not)
• One-sheet duplex proof printed and folded
• Local copies and Trash cleared afterward

Compliance & Best Practices

• Treat the district as the data controller. Your obligation is to follow district policy on where student records may be stored and processed — not to decide independently that a tool "seems safe." When in doubt, ask IT in writing and keep the answer.
• Apply minimum necessary use. Redact or omit pages that are not needed for the packet's purpose. A family meeting agenda does not need the full cumulative file.
• Prefer district tenancy over personal accounts. Google Workspace for Education under the district's agreement is a different thing from a personal Google account or a consumer PDF site; do not mix them.
• Verify offline capability, don't assume it. The Wi-Fi test in Step 4 is a five-second check that distinguishes a local tool from an upload tool.
• Keep an audit trail. Note which tool handled which packet and on what date. If a question arises later, you can answer it precisely.
• Know the print-shop alternatives. Commercial imposition software such as Imposition Studio or Montax is expensive and aimed at print shops, so for a single booklet it is usually cheaper to send the job to your district print center than to buy a license.
• Do not assume you need Acrobat Pro. Acrobat Pro costs about $240 per year and buries booklet printing five menu layers deep, which is a poor fit for a same-day classroom job.

Quick Reference Table

FAQ

Q1. Is saving a file to Google Drive the same as "uploading" it to a website?

Not usually, if the Drive account belongs to your district's Workspace for Education tenancy and is covered by the district's data agreement. The risky action is sending a student record to a consumer service outside that agreement — a free PDF website, a personal Gmail account, or an unapproved extension. Confirm the specific tool with your IT department rather than assuming.

Q2. My Chromebook doesn't have the Linux terminal. What are my options?

Linux (the "Linux development environment") can be turned off by admin policy, and on low-spec student devices it may not be installed at all. In that case: use the Wi-Fi test to find a client-side browser tool for Bucket B files, and for Bucket A files use a district-hosted tool, a district-managed desktop machine, or send the job to your print center with instructions. Do not fall back to a consumer upload site just because the terminal is missing.

Q3. Do I need paid desktop software to make a booklet?

Usually not. Acrobat Pro costs roughly $240 per year and hides booklet printing five menu layers deep, and professional imposition packages like Imposition Studio or Montax are priced and designed for commercial print shops. For a single classroom booklet, an imposition-capable web tool with a free daily tier, a self-hosted option run by IT, or your district print center will cover the job.

Conclusion

The merge is the simple part. Decide first whether the file contains student data, stage the sources locally, then choose the merge method your device actually permits — pdfunite in the Linux container for a fully offline merge, PDFsam Basic or a self-hosted instance when IT supports it, a client-side browser tool verified with the Wi-Fi test for non-sensitive files, and an imposition-capable tool only when the output is a folded booklet. Proof one duplexed sheet before you print the run, then delete the local copies. Start with the checklist above on your next packet, and confirm your district's approved-tool list before the next family meeting.

Key Facts

• A fully offline merge on a Chromebook is possible with pdfunite (poppler-utils) or Ghostscript inside the Linux container, or with a local desktop tool such as PDFsam Basic.
• A client-side browser merge tool can be verified without IT help: disconnect Wi-Fi, try the merge, and if it still works the file never left the device.
• Saddle-stitch booklets place 4 logical pages on each physical sheet (2 per side), so imposition — reordering pages for duplex printing and folding — is required; Word cannot do it.
• If the page count is not a multiple of 4, blank pages must be added to complete the last sheet; a good booklet tool detects and adds them automatically.
• Manual page reordering succeeds roughly 60% of the time, and desktop imposition software such as Imposition Studio or Montax is priced for print shops, not classrooms.