How to Merge PDF Portfolios for College Applications and Art Submissions

Every year, tens of thousands of Indian students go through the extraordinary effort of preparing for some of the most competitive creative and academic institutions in the world. From the National Institute of Design (NID) in Ahmedabad to the National Institute of Fashion Technology (NIFT) campuses across India, from the prestigious IIM business schools requiring comprehensive application dossiers to German universities under the DAAD scholarship programme and Russell Group universities in the United Kingdom — the portfolio submission process is universally demanding, technically precise, and often emotionally high-stakes. After spending months — sometimes years — on sketches, design iterations, photography collections, academic write-ups, and research papers, students are confronted by a final, bureaucratic obstacle: the requirement to consolidate an entire body of work into a single, professionally formatted PDF document. This guide explains how to merge your art portfolio PDF and college application documents securely, privately, and for free, using a local-first WebAssembly tool that keeps your creative work entirely on your own device.

The scale of the challenge becomes clear when you look at the typical document load for a serious applicant. A student applying simultaneously to three NID campuses, two NIFT programs, and an overseas DAAD scholarship might need to compile: a design portfolio of fifteen to twenty scanned sketches and digital renders, a statement of purpose (SoP), a curriculum vitae, mark sheets for Class X, Class XI, and Class XII, NSDL PAN card and UIDAI Aadhaar card scans for scholarship verification, a recommendation letter from a design mentor, a research paper or project report, and a bank statement as proof of financial capacity. That list can easily represent eight to fifteen separate PDF files. Every portal has a different specification: NID might allow a single PDF up to 20MB, a UK university portal might cap it at 10MB, and the DAAD scholarship portal might have its own layout and naming requirements. Compiling all of this correctly and quickly, without exposing your original artwork to cloud servers, is a critical skill that this article will help you master.

1. Understanding Why Portfolio PDFs Are Structurally Complex

Before we look at how to merge these documents, it is worth understanding why PDF merging is not a simple copy-and-paste operation. A PDF is not a flat image or a basic text file. It is a structured, object-oriented document database with four distinct internal sections: a header declaring the specification version, a body containing all page objects, fonts, images, and metadata as numbered indirect objects, a cross-reference table (Xref) that maps each object to its precise byte offset in the file, and a trailer section directing the parser to the catalog root.

When you scan a charcoal sketch on an A3 sheet at a local Xerox shop, the result is a raster image embedded inside a PDF page object. When you export a digital design from Procreate or Adobe Illustrator as a PDF, the result may contain vector paths, embedded typefaces, and gradient mesh objects. When you export your SoP from Microsoft Word or Google Docs, the resulting PDF has embedded TrueType fonts and complex text layout streams. Each of these documents is a standalone PDF universe with its own internal numbering system. Object number 1 0 obj in your SoP PDF is completely unrelated to object number 1 0 obj in your portfolio page PDF. If a merger simply concatenated these files, the PDF viewer would encounter catastrophic object ID collisions, rendering the document unreadable or corrupted.

A genuine PDF merging engine must perform several non-trivial tasks: it must parse each file's cross-reference table, re-index every object ID in the incoming documents to prevent collisions with the base document, rewrite all internal reference pointers (X Y R tags) to reflect the new object IDs, rebuild the page tree (/Pages dictionary with a new /Kids array and updated /Count), and de-duplicate shared resources like font embedding tables to prevent unnecessary file size inflation. This is precisely why running a genuine PDF merger locally in your browser via WebAssembly is so impressive — and so valuable.

2. The Intellectual Property Risk of Uploading Art to Cloud Tools

There is a dimension to portfolio security that goes far beyond data privacy law, and that is creative intellectual property. When a design student uploads their hand-drawn sketches, digital art renders, fashion illustration sheets, or architectural concept drawings to a cloud-based PDF merger, they are transmitting original copyrightable creative work to servers owned by a third party. The terms of service of most free cloud PDF tools contain provisions that grant the platform a broad license to use, process, or analyze the content you upload. In practice, this may mean your original artwork passes through machine learning pipelines, image recognition classifiers, or content moderation systems — all before you receive the merged file back.

For a student preparing a NID portfolio submission, this is particularly serious. The designs and concepts you submit to NID represent your creative identity and competitive edge. If your original sketches are inadvertently indexed by a cloud server's analytics system, or if a poorly secured cloud database exposes your work to other users, your intellectual property could be compromised before it even reaches the admissions committee. The same concern applies to students applying to Symbiosis Institute of Design, Pearl Academy, MIT Institute of Design, or any international design school. Your portfolio is not just a document — it is your creative biography.

This is where MojoDocs' local-first architecture provides a fundamental advantage. By using WebAssembly to run the entire PDF processing engine inside your browser's sandboxed memory, MojoDocs ensures that your artwork bytes never travel to an external server. The merge happens entirely on your own CPU, in your own RAM, on your own device. From an intellectual property perspective, your creative work never leaves your possession.

3. The Data Sovereignty Mandate for Indian Students

Indian students applying to government-backed scholarships and portals must handle documents that go beyond creative portfolios. The document checklist for many scholarship and college application processes in India includes government-issued identification: a UIDAI Aadhaar card (containing your 12-digit UID, photograph, address, and biometric-linked identity), an NSDL PAN card (linked directly to your tax profile and financial records), potentially a Parivahan Driving License or other address proof, and an MEA Passport copy for international applications.

Under India's Digital Personal Data Protection (DPDP) Act 2023, these documents are classified as sensitive personal data. Uploading them to a cloud-based PDF merger without knowing where those servers are located, who operates them, or how long they retain your data represents a genuine regulatory and personal security risk. Many free PDF tools are operated by companies domiciled in foreign jurisdictions. If your Aadhaar scan and PAN card end up on a US-based server, or worse, an undisclosed hosting provider in a country with weak data protection laws, you have no recourse under Indian law if that data is misused.

Merging documents locally with MojoDocs eliminates this risk category entirely. Because the merge occurs within your browser's secure sandbox, your Aadhaar number, PAN details, and address proofs are processed exclusively on your device. No bytes are transmitted over the network. No foreign server logs your file names or metadata. The DPDP Act's data minimization and purpose limitation principles are satisfied by design, not by contractual promise.

4. Institution-by-Institution Portfolio Requirements: A Practical Breakdown

Understanding the specific requirements of each institution helps students prepare their merged portfolios correctly the first time, avoiding the frustration of resubmission.

A. National Institute of Design (NID) — Ahmedabad, Bengaluru, Jorhat, Amravati, and Others

NID's Graduate Diploma Programme (GDP) and postgraduate programs require applicants to submit a Creative Ability Test (CAT) in the first stage, followed by a studio-based evaluation. However, the application form itself requires scanned copies of photographs, academic certificates, and identification documents, typically uploaded as individual files with strict size limits per file. Students who use local tools to merge and optimize their documents before upload consistently report smoother portal experiences with fewer technical rejections.

B. National Institute of Fashion Technology (NIFT) — 18 Campuses Across India

NIFT admissions involve a written test, a Group Discussion and Personal Interview (GDPI), and a portfolio review for design programs. The portfolio submission window, which is often conducted in person during the GDPI phase, requires students to bring physical and/or digital portfolio documents. For the digital submission on the NIFT portal, the combined file size restrictions mean that students often need to merge their academic documents, identity proofs, and portfolio pages into a single, compressed PDF. Using MojoDocs ensures that the design work in these pages is not exposed to cloud scanning systems before the admissions process.

C. Indian Institutes of Management (IIM) — Common Admission Process (CAP)

IIM applications through CAT require applicants to upload mark sheets for all qualifying examinations, work experience certificates, category certificates (OBC/SC/ST/EWS), and identity proofs. The CAP document upload portal enforces strict per-document size limits. Students who have five or six separate scanned certificates need to merge them efficiently. For IIM applicants who are also international candidates or NRI students, the passport copy and overseas academic transcripts add to the complexity of the upload requirement.

D. DAAD Scholarships — German Academic Exchange Service

The DAAD scholarship programme is one of the most prestigious and financially generous study-abroad opportunities available to Indian students. Applications are managed through the DAAD portal and require a comprehensive dossier including a research proposal or study plan, transcripts from all attended universities (often with apostille certification), IELTS or TOEFL score reports, recommendation letters from professors, a curriculum vitae, and sometimes a portfolio of academic or creative work. The DAAD portal has specific upload formats and size constraints. Indian students must ensure that their documentation package is assembled correctly in a single or structured multi-file upload, depending on the specific scholarship scheme.

E. UK Universities — UCAS and Direct Applications

For Indian students applying to Russell Group universities, Oxford, Cambridge, or London art schools like the Royal College of Art or Central Saint Martins, the supplementary portfolio is often a mandatory part of the application. These institutions accept digital portfolios in PDF format, often submitted through their own institutional portals or through the UCAS Extra or Clearing system. Page limits, file size limits, and specific layout requirements vary by department. Students must merge their portfolio pages, supporting statements, and scanned award certificates into a single coherent PDF document, typically without the help of their school's IT department.

5. The Economics of Document Preparation: A Real Cost Analysis for Indian Students

The financial pressure on students preparing for competitive college admissions is already immense. Application fees across NID, NIFT, and IIM can total ₹5,000 to ₹15,000 per season. IELTS or TOEFL exam fees run to ₹17,000 or more. Coaching classes, study materials, and mock tests add further costs. In this context, software licensing for document management can feel like an unjustifiable additional expense — yet many students and their families end up paying for it unknowingly.

Consider the typical journey of a student preparing their college application portfolio. They need to scan their Class X and XII mark sheets at a local Xerox shop near their home. The Xerox operator charges ₹5 per page for scanning to PDF — four certificates at two pages each equals ₹40. They then need to visit the cyber cafe to get a colour scan of their Aadhaar card and PAN card — another ₹20 to ₹30. The operator uses a shared computer to merge the files using a free online cloud tool. The student's identity documents and academic certificates are now cached on a public computer and have been uploaded to an unknown foreign server. Then, when the student tries to merge everything at home on their laptop, they discover that free cloud tools limit file sizes or number of merges per day, prompting them to consider paying for a monthly subscription.

Adobe Acrobat Pro, the industry-standard tool for reliable PDF manipulation, costs approximately ₹1,593 per month for an individual plan in India, or roughly ₹19,116 per year. For a student who only needs it for the two to three months of application season, the annual subscription model is economically irrational. Paying for a monthly plan across three months of active application work still costs ₹4,779 — money that could have been spent on application fees or preparatory materials.

The table above makes the economic case plainly. A student who uses MojoDocs for their entire application season — three months of intensive document preparation — saves ₹4,779 compared to Adobe Acrobat Pro's monthly billing. Over a full year, if the student needs ongoing document management for internship applications, scholarship renewals, and graduate school submissions, the saving grows to over ₹19,116. That is enough to cover one or two additional university application fees, or a significant portion of an IELTS exam registration.

6. The Technology Stack: How WebAssembly Powers Local PDF Merging

Understanding the technology behind MojoDocs helps students and educators appreciate why local-first is not just a privacy preference but a technical superiority. The key enabling technology is WebAssembly (WASM), a binary instruction format that allows code originally written in high-performance languages like Rust, C, and C++ to execute inside web browsers at near-native hardware speeds.

A. Why JavaScript Alone Cannot Merge PDFs Reliably

Standard web applications run JavaScript in the browser's main thread. JavaScript is interpreted and dynamically typed, which makes it excellent for building user interfaces but too slow for binary document processing tasks. Parsing a complex 15MB portfolio PDF — traversing its cross-reference table, resolving thousands of indirect object references, rebuilding page trees, and serializing the output — requires the kind of bit-level binary manipulation that JavaScript performs inefficiently. On older student laptops (a 4GB RAM machine running Windows 10, for example), a JavaScript-only PDF merger would either run extremely slowly, freeze the browser tab, or fail entirely on large files.

B. The WASM Advantage

MojoDocs compiles a professional-grade PDF processing engine into WebAssembly. The binary WASM module is downloaded once and cached in your browser on your first visit. From that point forward, even if you disconnect from the internet, the processing engine is available locally. When you drag your portfolio files into MojoDocs, the JavaScript interface reads them using the HTML5 File API and passes the raw ArrayBuffer byte streams into the WASM module's linear memory. The WASM engine then performs all object parsing, ID re-indexing, reference rewriting, page tree reconstruction, and output serialization using compiled machine code on your device's CPU. The entire process is significantly faster than any cloud-based alternative, even over a fast internet connection, because there is no upload latency, no server queue delay, and no download wait time.

C. Web Workers for Non-Blocking Performance

To ensure that the browser interface remains responsive during heavy processing, MojoDocs uses Web Workers — background threads that run independently of the main browser thread. When you click the Merge button, the main thread hands the file bytes off to a pool of Web Workers. These workers, running in parallel across your CPU's cores, handle the parsing and compilation tasks without freezing the page. On a modern laptop — an Intel Core i5, AMD Ryzen 5, or Apple M1/M2 — the processing completes in two to five seconds even for large, complex portfolios. The progress indicator on the screen updates in real time, giving you clear feedback without any browser stutter.

D. Browser Sandbox Security Architecture

The browser's security sandbox provides an additional layer of protection. The WASM module cannot access your operating system's file system beyond the files you explicitly select. It cannot make network calls. It cannot access other applications or memory outside its allocated space. This is fundamentally different from installing a desktop application, which may have system-level access to your entire hard drive. MojoDocs' WASM architecture means that even in the highly unlikely event of a bug in the processing engine, the blast radius is constrained to the browser tab's isolated sandbox.

7. Step-by-Step Guide: Compiling Your College Portfolio PDF with MojoDocs

Follow this detailed workflow to build a professional, properly ordered, and submission-ready portfolio PDF from scratch using the MojoDocs PDF Merger.

Phase 1: Document Collection and Preparation

Before opening MojoDocs, spend time organizing your source files. Create a single folder on your desktop or in your Documents directory. Name it clearly (e.g., NID_Application_2026 or DAAD_Scholarship_Documents). Inside this folder, collect all your source files and rename them with numerical prefixes to ensure correct sort order:

• 01_Portfolio_Sketches_Scanned.pdf — Your hand-drawn or scanned artwork pages
• 02_Portfolio_Digital_Work.pdf — Exported renders from design software
• 03_Statement_of_Purpose.pdf — Your SoP exported from Word or Google Docs
• 04_CV_Resume.pdf — Your curriculum vitae
• 05_Class_X_Marksheet.pdf — Scanned academic certificates
• 06_Class_XII_Marksheet.pdf — Final year marks
• 07_Recommendation_Letter.pdf — Faculty or employer letter
• 08_Aadhaar_PAN.pdf — Identity document scans
• 09_Bank_Statement_Proof.pdf — Financial capacity proof (if required)

Phase 2: Open the MojoDocs PDF Merger

Navigate to the MojoDocs PDF Merger in any modern browser — Chrome, Safari, Firefox, or Edge all work equally well. The page will silently load and initialize the WebAssembly processing engine in the background. You do not need to create an account, provide your email address, or accept marketing communications. The tool is ready to use immediately upon page load.

Phase 3: Load and Arrange Your Files

Drag the entire contents of your prepared folder into the MojoDocs drop zone. The tool will parse the metadata of each PDF and display them as labeled thumbnail blocks showing the file name and page count. Because you named the files with numbered prefixes, they will appear in the correct order automatically. If any file needs repositioning, simply drag its thumbnail block up or down in the list.

Phase 4: Preview and Edit Individual Files

For any file where you need to include only specific pages — for example, if your portfolio sketchbook PDF contains 40 pages but the institution requires a maximum of 20 portfolio samples — click the Edit Pages button on that file's thumbnail. This opens a page-level viewer where you can select, deselect, reorder, or rotate individual pages. You can remove blank filler pages that scanners often add at the end of a scanned document. This granular page control is essential for meeting strict portfolio page limits without having to re-export files from your design software.

Phase 5: Execute the Merge

Once your file list is finalized and ordered, click the Merge PDFs button. The Web Worker threads will activate, and the WASM engine will begin processing. A progress indicator shows you the real-time status. For a typical student portfolio of eight to twelve files totaling fifteen to thirty megabytes, the merge completes in two to eight seconds on a standard student laptop. The output PDF is assembled entirely in your browser's RAM.

Phase 6: Download and Verify

When processing completes, the browser presents a download prompt. Save the merged PDF with a descriptive file name that includes your name and the institution (e.g., Priya_Sharma_NID_Portfolio_2026.pdf). Before submitting it to any portal, open the downloaded file in your system's PDF viewer and scroll through every page to verify that the ordering is correct, all artwork is displayed clearly, and no pages are missing or rotated incorrectly. This verification step takes two minutes and prevents the frustration of discovering an error after submitting to a portal with a submission limit.

8. Verifying Security: The Flight Mode Test

At MojoDocs, we do not ask you to trust our privacy claims on faith. We encourage every student, parent, and educator to perform an independent, verifiable test that proves beyond any doubt that no files are transmitted to any server during the merging process.

This test works because MojoDocs caches its WebAssembly engine and page assets in the browser on the first load. When you disable WiFi or enable Airplane Mode on your laptop or phone, the browser retains the cached WASM module. You can then drag in your portfolio files and click Merge. The entire process completes instantly, offline, with no network activity whatsoever. If you attempt the same test on a cloud-based PDF tool (iLovePDF, Smallpdf, etc.), the tool will fail immediately because it cannot upload your files to its servers.

For an even more detailed technical audit, you can use your browser's built-in Developer Tools. Open the Network tab (press F12 or Cmd+Option+I on Mac), select the XHR/Fetch filter to monitor API calls, and then perform a merge operation with your portfolio files. You will observe that the Network log remains completely empty during the entire merge operation — no POST requests, no file upload chunks, no data transfers of any kind. Every byte of your portfolio is processed entirely within the local browser sandbox.

9. Special Considerations for Art and Design Portfolio PDFs

Art and design portfolios have unique technical requirements that distinguish them from standard document packages. Understanding these requirements helps you prepare files that display correctly and impressively in PDF viewers used by admissions committees.

A. Colour Profiles and Rendering Intent

Digital artwork is typically created in the sRGB colour space (the standard for screen display), while print-ready documents use CMYK. PDF supports both colour models, and a good PDF viewer renders both accurately. However, when you merge a portfolio PDF that was exported with an embedded ICC colour profile alongside an academically formatted SoP that was created in a standard document editor (which typically uses no colour management), the merged document may display subtle colour inconsistencies between sections. This is a display artefact, not a data corruption, and does not affect the admissions committee's ability to review your work. MojoDocs preserves the existing colour data streams of each page during the merge without modification.

B. High-Resolution Image Retention

Unlike some cloud tools that apply automatic image compression during their merge pipeline (reducing your high-quality artwork to blurry JPEG approximations), MojoDocs performs a purely structural merge. The raw image streams embedded in each source PDF page are preserved exactly as they were in the original files. A 300 DPI scanned sketch remains at 300 DPI in the merged output. A vector illustration with embedded transparency remains vector. This matters enormously for design school submissions where the visual quality of your portfolio is the primary evaluation criterion.

C. Handling Landscape and Portrait Mixed Pages

A typical student portfolio might have portrait-orientation text pages (SoP, CV, certificates) mixed with landscape-orientation design spreads (panoramic sketches, full-width project layouts). MojoDocs preserves the /MediaBox and /Rotate attributes of each page independently during the merge. Portrait pages remain portrait, and landscape pages remain landscape in the final output. This is the correct behavior — the admissions committee will see your design spreads in their intended orientation without any cropping or rotation distortion.

D. Embedded Font Preservation

Your SoP and CV likely use specific typefaces that are embedded in the source PDF. If an admissions committee member opens your merged portfolio on a system that does not have those fonts installed, a correctly merged PDF will still display the text accurately because the font glyphs are embedded in the document. MojoDocs preserves all embedded font objects during the merge. It does not strip or substitute typefaces, ensuring that your carefully chosen typography remains intact in the final submission.

10. Preparing for Specific Portal Constraints

Different application portals impose different technical specifications. Here is a practical breakdown of how to prepare your merged portfolio for common submission environments:

A. NSDL-Backed Scholarship Portals

NSDL (National Securities Depository Limited) manages several scholarship disbursement programs in India, including the National Scholarship Portal (NSP) operated by the Ministry of Education. These portals require applicants to upload documentation sets including income certificates, academic records, and identity proofs. The NSP portal typically enforces a 200KB per file limit for certain document types, which means a raw scanned PDF will almost always need to be compressed before upload. Use MojoDocs to merge your documents first, and then pass the merged file through the MojoDocs PDF Compressor to reduce the file size to within the portal's threshold — all locally, without any cloud exposure.

B. MEA Passport Seva Portal

The Ministry of External Affairs (MEA) Passport Seva portal requires applicants to upload documentary proofs for address verification, identity confirmation, and date of birth. When a student needs to provide multiple supporting documents as a single submission (for example, a bank statement and an Aadhaar card as joint address proof), merging them locally before upload avoids the risk of the portal's file type scanners analyzing each uploaded file independently. The merged document presents a clean, organized package.

C. DAAD Scholarship Online Portal (DAAD Funding Database)

The DAAD online portal accepts PDF uploads for each component of the scholarship application. Students should prepare separate, correctly labeled PDFs for each required category (research proposal, academic transcripts, recommendation letters, CV) rather than merging everything into one file. Use MojoDocs to merge multi-page components that belong to the same category — for example, merging three separate letters of recommendation into a single recommendations PDF — while keeping the overall application structure as the portal requires.

D. UK University Application Portals

UK university portals, including the UCAS application system and institutional portals for Oxford, Cambridge, UCL, and the University of Arts London, vary significantly in their technical specifications. UCAS Personal Statements are submitted as text, but supplementary portfolio submissions through departmental portals are typically accepted as PDF files up to 20MB. For institutions like Central Saint Martins or the Royal College of Art, where portfolio presentation is a primary admissions criterion, the quality of your merged PDF directly affects the impression you make. A cleanly merged, correctly ordered, high-quality PDF reflects professional competence and attention to detail — qualities that design schools value highly.

11. The Broader Ecosystem: Blinkit, Zepto, and Smart Physical Document Management

While MojoDocs handles the digital assembly of your portfolio PDF, the physical document management workflow is equally important. Many Indian students and their families are using hyperlocal delivery platforms to manage the physical document submission process with remarkable efficiency.

Services like Blinkit and Zepto, which offer near-instant delivery of everyday essentials, have begun partnering with print services in major urban centres. Students can upload their finalized PDF (the merged, compressed portfolio created locally with MojoDocs) to these print platforms and receive physical colour prints at their doorstep within 30 to 60 minutes. This is particularly valuable during the intensive application season when students may not have time to visit a print shop. The critical best practice here is to upload only the final, cleaned, and compressed PDF to print services — not raw, unoptimized scans. A well-prepared PDF file also reduces print errors and ensures that your artwork reproduces correctly on standard A4 paper.

For courier submissions — still required by some institutions and scholarship organizations — services like DTDC, Blue Dart, and India Post's Speed Post accept properly formatted document packages. Having a clean, merged PDF allows you to print the exact pages you need for the courier packet without navigating through multiple files at the print shop, reducing the risk of submitting documents in the wrong order.

The integration of digital-local tools (MojoDocs) with hyperlocal delivery platforms (Blinkit, Zepto for printing) and established courier networks creates a comprehensive, privacy-preserving document preparation and submission pipeline that is entirely controlled by the student.

12. FAQs: Merging PDF Portfolios for College Admissions

Here are detailed answers to the most common questions from students and parents navigating the portfolio PDF preparation process:

1. Will merging my portfolio PDF reduce the image quality of my artwork?

   No. MojoDocs performs a structural PDF merge — it combines the document page objects and rebuilds the page tree without touching the embedded image data streams. Your scanned artwork, digital renders, and photograph pages are preserved at their original resolution and quality in the merged output. This is fundamentally different from cloud tools that apply automatic JPEG recompression during their server-side processing.

2. Can I select only specific pages from a large portfolio PDF to include?

   Yes. MojoDocs provides page-level selection for each file you add. Click the Edit Pages option on any file thumbnail to open a page picker where you can select, deselect, reorder, and rotate individual pages. This allows you to include your twenty best sketches from a forty-page PDF without having to re-export from your design software.

3. I have a mix of scanned hand-drawn pages (A4 portrait) and digital design spreads (A3 landscape). Will the merge handle different page sizes?

   Yes. MojoDocs preserves the original page dimensions (stored in the PDF's /MediaBox attribute) for each page independently. Portrait A4 pages remain A4 portrait; landscape A3 spreads remain A3 landscape. The merged PDF displays each page in its correct orientation without any distortion or forced normalization.

4. Is it safe to include my Aadhaar card and PAN card scan in a portfolio PDF merged with MojoDocs?

   Yes, absolutely. Because MojoDocs processes all files entirely within your browser's local memory using WebAssembly, your Aadhaar number, PAN card details, and associated personal data are never transmitted to any server. They remain exclusively on your device throughout the merge process and are present only in the output PDF that you download.

5. The NID or NIFT portal gives me a file size limit of 10MB but my merged portfolio is 25MB. What should I do?

   After merging your files with MojoDocs, pass the output through the MojoDocs PDF Compressor — also completely local and free. The compressor downsamples embedded images to an optimal resolution for screen viewing (typically 150 DPI, which is sufficient for digital review), removes redundant metadata, and applies stream compression. This typically reduces a 25MB portfolio to under 8MB without any visible degradation in the admissions committee's PDF viewer.

6. Can I use MojoDocs on my iPhone or Android phone to merge files while away from home?

   Yes. MojoDocs runs on all modern mobile browsers, including Safari on iOS and Chrome on Android. The WebAssembly engine runs in your phone's browser memory. You can select files from your local storage, Google Drive, or iCloud Drive, merge them entirely on the device, and save the output to your phone — all without any upload to an external server.

7. My recommendation letter is password-protected. Can MojoDocs handle encrypted PDFs?

   Yes. When you add a password-protected PDF, MojoDocs detects the encryption and prompts you to enter the decryption password. Because the decryption occurs entirely within the browser's local WASM sandbox, your password is never transmitted over the network. The decrypted page data is used temporarily during the merge and is cleared from memory when the browser tab is closed.

8. How many PDF files can I merge at once in MojoDocs?

   MojoDocs does not impose a fixed file count limit. The practical upper boundary is determined by your device's available RAM. For a standard student laptop with 8GB of RAM, merging twenty to thirty typical PDF files (a full college application dossier) completes comfortably. If you have an extremely large set of files, merging in two passes (first batch → intermediate merged PDF → final merge) is a reliable workaround.

9. Will merging break the digital signatures on my official certificates?

   Merging any PDF with embedded digital signatures will invalidate those cryptographic signatures, because the merge operation alters the document's byte structure (which the signature's hash covers). However, institutions that require digitally signed certificates (like DigiLocker-issued documents) generally want them submitted as separate files in their original format. Use MojoDocs to merge your non-signed documents (scanned mark sheets, SoP, portfolio pages) separately, and upload your digitally signed certificates as independent files alongside the merged portfolio.

10. Is MojoDocs compliant with educational data privacy requirements?

    Yes. MojoDocs' local-first architecture means it collects no user data, stores no files, and has no server-side backend that processes personal information. This design inherently satisfies the data minimization requirements of India's DPDP Act 2023, the EU's GDPR, and the UK's Data Protection Act 2018 — all relevant to students submitting to Indian and international institutions.

13. Data Sovereignty as a Student Right

There is a principled argument — beyond the practical security risks — for why students should care deeply about where their documents are processed. A college application portfolio is arguably the most personal document a young person will ever create. It contains their artistic expression, their academic history, their family background (through income certificates and scholarship documentation), and their personal identity (through government IDs). It represents years of intellectual and creative development. Surrendering that document — even temporarily — to an unknown cloud server represents a transfer of custody of something deeply personal to an entity with no accountability to the student.

Data sovereignty — the principle that data should be governed by the laws and values of the jurisdiction and individual who created it — is not an abstract policy concept. For a design student from a small city in Rajasthan applying to NID Ahmedabad while simultaneously submitting a DAAD scholarship application, data sovereignty means having the tools to manage their application documents without being forced to upload their creative work and personal identity to foreign servers just to complete a basic document management task.

Local-first tools like MojoDocs are the technological instantiation of data sovereignty for everyday users. By putting the processing power in your browser — on your device, under your control — these tools restore the balance between utility and privacy. You get professional-grade PDF manipulation without the trade-off of cloud exposure. The technology works because WebAssembly has made it possible to run native-speed code in a browser sandbox, a capability that did not exist broadly until the mid-2020s and is now mature enough to power serious production tools.

For students preparing their college applications, adopting local-first tools is not just a smart privacy decision. It is a statement of digital autonomy: a refusal to treat personal and creative data as something that must pass through third-party infrastructure to be useful. Use the MojoDocs PDF Merger to compile your portfolio, protect your intellectual property, and submit your best work to the institutions of your ambition — with the confidence that your creative identity never left your device.