Most "how I built this" posts skip the boring part — the server. But if you're thinking about building your own free tool site, that's actually the part that decides whether it survives its first busy day or crashes the moment ten people upload a file at once. Here's exactly what SmallPDF.us runs on, why we picked it, and what we'd tell you before you spend a rupee.

<h2>Why a VPS, not shared hosting</h2>

Shared hosting is fine for a blog or a brochure site. It falls apart the moment your app does real work — and PDF processing is real work. Compressing a 50MB file, running OCR on a scanned document, or converting a PowerPoint to PDF all need actual CPU and memory for a few seconds at a time. Shared hosting plans throttle exactly that kind of burst usage, which is why our tools would randomly time out or hang if we tried to run them there.

A VPS (Virtual Private Server) gives you a dedicated slice of CPU, RAM, and disk that's yours alone — nobody else's traffic spike slows you down, and you're not fighting shared limits when five people compress a PDF at the same time.

<h2>What we actually run</h2>

SmallPDF.us runs on a <a href="https://www.hostinger.com/in?REFERRALCODE=1MANIKANT90" target="_blank" rel="noopener noreferrer">Hostinger VPS</a>. A few practical reasons that plan works for a site like this:

- Enough RAM headroom to run multiple Node.js processes side by side (we run the frontend, the API, and background cleanup jobs all on one box)
- NVMe storage, which matters more than people expect — file uploads, temporary conversion files, and database reads all hit disk constantly on a tool site
- Root access, so we can install exactly what conversion libraries and dependencies each tool needs, instead of being stuck with whatever a shared host allows

For context on cost: a VPS plan with enough resources for a small-to-medium tool site typically runs $5-15/month to start, which is a lot cheaper than people assume before they check.

<h2>The stack on top of it</h2>

The server itself is just the foundation. On top of it:

- <strong>Next.js</strong> for the frontend — handles all 24 tool pages, SEO, and the multi-language support
- <strong>Node.js + Express</strong> for the backend API that actually does the file conversion work
- <strong>SQLite</strong> for the database — simple, file-based, and plenty fast for a site this size (no need for a separate database server)
- <strong>PM2</strong> to keep the Node processes running and auto-restart them if anything crashes
- <strong>Nginx</strong> in front of everything, handling SSL and routing traffic to the right service

None of this is exotic. The point isn't to use fancy technology — it's to pick boring, reliable tools that don't need babysitting.

<h2>What we'd tell you before you start</h2>

<strong>Auto-delete your uploaded files.</strong> A tool that processes user files will fill up your disk fast if you don't clean up after every job. We auto-delete everything within 2 hours.

<strong>Rate-limit everything from day one.</strong> The first thing that will hit your server hard isn't real traffic — it's bots and scrapers. Build rate limiting in before launch, not after your VPS falls over.

<strong>Start smaller than you think you need.</strong> You don't need a huge server on day one. It's much easier to upgrade a VPS plan later than to pay for capacity you're not using yet.

<h2>Frequently Asked Questions</h2>

<h2>Do I need a VPS to start, or can I use shared hosting first?</h2>
If your site is genuinely doing file processing (not just serving static pages), skip shared hosting. It'll cost you more in frustration than a VPS costs in dollars.

<h2>How much traffic can a basic VPS handle?</h2>
It depends entirely on what each request does. A VPS that handles thousands of simple page views easily might struggle with a few dozen simultaneous PDF conversions, because conversion work is CPU-heavy in a way page views aren't.

<h2>Is it hard to set up if I'm not a sysadmin?</h2>
It's more approachable than it sounds. Most providers, including Hostinger, offer one-click app installs and managed panels that handle the basic server setup — you don't need to be a Linux expert to get a Node.js app running.

Building your own tool site isn't magic — it's a normal web app with a few extra things to think about around file handling and cleanup. If you're thinking about it, the hosting decision is the first real one to make, and it's worth getting right before you write a line of code.


How We Built SmallPDF.us: The Hosting and Stack Behind Our Free PDF Tools

"Should I send this as a PDF or a Word document?" It's a question that comes up constantly — for resumes, contracts, reports, and everyday files — and the wrong choice can genuinely cause problems, from a hiring manager's system mangling your resume formatting to a client editing a contract they shouldn't be able to touch.

Here's a clear way to think about it, plus how to convert between the two when you need to.

<h2>The Core Difference: Fixed vs Editable</h2>

A Word document (.doc or .docx) is built to be edited. Formatting can shift depending on the software, font availability, or screen size — open the same .docx in Word, Google Docs, and LibreOffice and you might see slightly different spacing or page breaks.

A PDF is built to look identical everywhere. Fonts, spacing, and layout are locked in, so the document looks exactly the same whether it's opened on a phone, a laptop, or printed out. That's the entire point of the format — "Portable Document Format."

That one difference — editable vs fixed — decides almost every use case below.

<h2>When to Use PDF</h2>

- Sending a final version of anything — contracts, invoices, official reports, signed agreements
- Resumes and cover letters, in most cases — a PDF guarantees your careful formatting doesn't break on someone else's computer
- Anything with precise layout — flyers, certificates, forms with specific field positions
- Documents you don't want casually edited — a PDF isn't uneditable, but it raises the bar enough to prevent accidental changes
- Archiving — PDFs are a stable, long-term format that will still open correctly years from now

<h2>When to Use Word</h2>

- Any document that's still being worked on — drafts, collaborative reports, anything with more edits coming
- Templates you're handing off for someone else to fill in or customize
- Documents that need tracked changes or comments during review
- Long-form content where the recipient may want to reformat, repurpose, or reuse sections of the text

A simple rule of thumb: if the document's job is finished, make it a PDF. If the document's job is still in progress, keep it a Word file.

<h2>The Resume Exception</h2>

Resumes deserve a specific note, since this comes up so often. Most companies now use Applicant Tracking Systems (ATS) that scan resumes for keywords before a human ever sees them. Modern ATS software reads PDFs just fine in the vast majority of cases, and a PDF protects your formatting — so PDF is the safer default.

The one exception: if a job posting explicitly asks for a Word document, follow that instruction. Some older or custom-built application systems still parse .docx more reliably than PDF.

<h2>Converting Between the Two</h2>

You don't need to pick one format and stick with it forever — converting is quick:

- Need a Word file as a PDF? Use <a href="/word-to-pdf">Word to PDF</a> — formatting, images, and layout carry over automatically
- Need to edit a PDF as a Word document? Use <a href="/pdf-to-word">PDF to Word</a> — text becomes editable, though very complex layouts (multi-column designs, heavy graphics) may need minor cleanup after conversion
- Only need to fix a typo or update a date in a PDF without converting it at all? Our <a href="/edit-pdf">Edit PDF</a> tool lets you click any text in a PDF and retype it directly — no conversion round-trip needed

<h2>Common Mistakes</h2>

- Sending a Word document as a "final" version — the recipient's software can silently reformat it, and anyone can edit it further
- Converting PDF to Word just to make one small text change — for simple edits, converting and reconverting a whole document is more work (and more risk of formatting breaking) than just editing the PDF directly
- Assuming a scanned PDF is the same as a "real" PDF — a scanned document is really just an image; if you need to search or edit the text, it needs OCR first

<h2>Frequently Asked Questions</h2>

<h2>Does converting PDF to Word ever break formatting?</h2>
Simple documents (mostly text, standard layout) convert cleanly. Complex designs with multiple columns, text boxes, or heavy graphic elements may need some manual adjustment after conversion — this is a limitation of any PDF-to-Word converter, not specific to one tool.

<h2>Is a PDF actually harder to edit than Word?</h2>
It's not harder, just different — Word edits text directly, while a PDF stores a fixed layout. For quick fixes like updating a date or number, editing the PDF directly is usually faster than converting to Word, editing, and converting back.

<h2>Which format is better for printing?</h2>
PDF, without question. Since layout is fixed, what you see on screen is exactly what prints — Word documents can shift slightly between printers and driver versions.

Whichever direction you need to go, both conversions are free and run entirely in your browser: <a href="/pdf-to-word">PDF to Word</a> and <a href="/word-to-pdf">Word to PDF</a>.


PDF vs Word: Which Format Should You Use and When?

Contracts, tax documents, medical records, financial statements — a lot of what ends up as a PDF is exactly the kind of thing you don't want opened by anyone who stumbles across the file. Password-protecting a PDF takes less than a minute and means the document is useless to anyone without the password, even if it ends up in the wrong inbox or on a shared drive.

Here's how to do it properly, plus a few things worth knowing before you send a protected file.

<h2>Why Password-Protect a PDF</h2>

- You're emailing something sensitive — a signed contract, an ID scan, a payslip — and want a second layer of protection beyond "hope no one else checks that inbox"
- You're storing files on a shared or cloud drive where more people than intended might have access
- You're sending a document to a client or vendor and want to control who can actually open it
- Compliance or company policy requires sensitive documents to be encrypted before sharing

A password doesn't just add a polite request not to look — a properly protected PDF is genuinely encrypted, so the content is unreadable without the correct password.

<h2>Step-by-Step: Protecting Your PDF Online</h2>

- Open our <a href="/protect-pdf">Protect PDF</a> tool
- Upload the PDF you want to secure
- Enter a password (see the section below on choosing a strong one)
- Download the protected file — that's the version you should send or store

The tool encrypts the file using AES-256, the same standard used by banks and government systems, so the protection is real, not cosmetic. Your original file and the password are never stored on our servers — everything is processed and then deleted.

<h2>Choosing a Strong Password</h2>

A weak password defeats the point of encrypting the file in the first place. A few practical guidelines:

- Use at least 10-12 characters — longer is always stronger
- Mix letters, numbers, and a symbol or two
- Avoid anything guessable from the document itself — a contract's password shouldn't be the client's name or the date on the file
- Don't reuse a password you already use for email or banking — if the PDF password ever leaks, you don't want it exposing anything else

If you're sending the protected file to someone else, share the password through a different channel than the file itself — a text message or phone call, not the same email thread. If both travel together in one email, the password offers no real protection.

<h2>What If You Need to Remove a Password Later</h2>

If you already know the password and just need to remove it — say, the document no longer needs to be restricted, or you're the one who set the password and now need an unlocked copy for internal use — our <a href="/unlock-pdf">Unlock PDF</a> tool removes it in seconds.

One important note: this only works when you have the password. There's no way to bypass or recover a password you've genuinely lost — that's exactly what makes the encryption meaningful. If you're setting a password on an important document, keep a copy of it somewhere safe (a password manager, not a sticky note).

<h2>A Few Things Password Protection Won't Do</h2>

- It won't stop someone from screenshotting or photographing the content once they've entered the correct password
- It doesn't watermark or track the document — protection just controls who can open it
- If you need to prevent editing or printing specifically (rather than restrict opening), that's a different kind of PDF permission — most protection tools, including ours, focus on the "who can open this file" layer, which is what matters for the vast majority of sensitive-document use cases

<h2>Frequently Asked Questions</h2>

<h2>Is browser-based PDF protection actually secure?</h2>
Yes, as long as the file is transferred over an encrypted connection (look for https) and the service doesn't retain your files or passwords afterward — both are true here. The encryption applied to the PDF itself (AES-256) is independent of how you accessed the tool.

<h2>Can I protect multiple PDFs with the same password?</h2>
You can, though for genuinely sensitive documents it's better practice to use a unique password per file or per recipient — that way, if one password is ever compromised, it doesn't expose everything else.

<h2>Will the recipient need special software to open a protected PDF?</h2>
No — any standard PDF reader (Adobe Reader, Preview, browser PDF viewers, etc.) will prompt for the password and open the file normally once it's entered correctly.

Protecting a PDF takes about as long as it took to read this article. Try it on your next sensitive document with our free <a href="/protect-pdf">Protect PDF</a> tool.


How to Password Protect a PDF (Step-by-Step Guide)

If you've ever tried to email a PDF and gotten a bounce-back message saying the file is "too large to send," you're not alone. Most email providers cap attachments somewhere between 10MB and 25MB, and it doesn't take much — a scanned contract, a few high-resolution photos, a design proof — to blow past that limit.

The good news: you almost never need the file at its original size to send it. Compressing a PDF for email usually takes under a minute and, done right, the recipient won't notice any difference in quality.

<h2>Why Emails Reject Large PDFs</h2>

Email attachment limits exist because mail servers weren't built to move huge files efficiently — every attachment gets copied and stored multiple times as it travels from your outbox to the recipient's inbox. Common limits look like this:

- Gmail: 25MB per email
- Outlook / Microsoft 365: 20MB (sometimes 10MB on older plans)
- Yahoo Mail: 25MB
- Many corporate mail servers: 10MB or less

If your PDF is anywhere near these numbers, there's a good chance it either gets rejected outright or silently fails to send.

<h2>How to Compress a PDF for Email in Under a Minute</h2>

You don't need Adobe Acrobat or any desktop software for this. Here's the fastest way:

- Go to our <a href="/compress-pdf">Compress PDF</a> tool
- Drag in your file (or click to browse)
- Pick a compression level — "Recommended" works for most email use cases
- Download the smaller file and attach it to your email

The whole process runs in your browser and the file is processed securely — nothing is stored longer than needed, and it's auto-deleted from our servers afterward.

<h2>What Actually Makes a PDF Large</h2>

Understanding what bloats a PDF helps you avoid the problem next time:

- High-resolution images embedded at print quality (300 DPI) when 150 DPI is plenty for screen viewing
- Scanned pages saved as full-color images instead of black-and-white or grayscale
- Embedded fonts, especially if the same font is embedded multiple times across pages
- Leftover metadata, layers, or annotations from editing software

A 20-page contract with a company logo on every page can easily hit 15-20MB if the logo image wasn't optimized before being placed in the document.

<h2>Which Compression Level Should You Pick</h2>

Most compression tools, including ours, offer a few levels:

- Light compression keeps quality nearly identical to the original — best if the PDF has diagrams, screenshots with fine text, or anything you might print
- Recommended (balanced) compression is the right default for email — it typically cuts file size by 60-90% with no visible quality loss on screen
- Strong compression pushes file size down further and is best when you just need the file under a hard limit and image quality isn't critical

If you're not sure, start with the recommended setting. You can always compress again with a different level if the result isn't small enough.

<h2>Other Ways to Shrink a PDF Before You Even Compress It</h2>

If compression alone doesn't get you under the limit, a few quick fixes often help:

- Remove blank or unnecessary pages before compressing — use our <a href="/split-pdf">Split PDF</a> tool to extract only the pages you need
- If you're scanning a physical document, scan at a lower resolution (150-200 DPI is fine for text documents) instead of compressing a huge scan afterward
- Combine only what's needed — if you're merging several files, check whether the recipient actually needs all of them in one PDF

<h2>Frequently Asked Questions</h2>

<h2>Will compressing noticeably reduce quality?</h2>
At the recommended setting, most people can't tell the difference on screen. Compression mainly targets image data, which is usually the biggest contributor to file size — text and vector graphics stay sharp.

<h2>Is it safe to upload a PDF with sensitive information?</h2>
Yes. Files are transferred over an encrypted connection, processed, and automatically deleted from our servers within a set time window — we don't keep copies or share your documents.

<h2>What if the file is still too big after compressing?</h2>
Try a stronger compression level, or check whether the PDF actually needs to be one file — splitting it into smaller parts and sending only the relevant pages is often the better fix for very large documents.

Compressing a PDF for email is one of those small tasks that saves a surprising amount of back-and-forth. Try our <a href="/compress-pdf">free PDF compressor</a> next time a file bounces back — no signup, no software to install, and your file stays private.


How to Compress a PDF for Email Without Losing Quality

Most people don't think about PDFs until one goes wrong — a file too big to email, a scanned contract you can't rearrange, a report you need in Word instead. The fixes for all of these are simple, but only if you know which tool actually does the job. Here's a practical rundown of the four tasks that come up constantly, and how to handle each one in under a minute.

<h2>Compress PDF — When a File Is Too Big to Send</h2>

This is usually the first PDF problem people hit. A scanned contract, a deck full of screenshots, or a report with embedded images can easily blow past the 10-25MB limit most email providers enforce.

The fix is almost always the images inside the file, not the text. A <a href="/compress-pdf">PDF compressor</a> re-encodes those images at a size appropriate for screen viewing instead of print, which is usually where 80-90% of a bloated file's size is actually coming from. Recommended-level compression keeps the document looking identical on screen while cutting the file down enough to attach anywhere.

Good for: email attachments, upload forms with a size cap, faster page loads if you're hosting the PDF on a website.

<h2>Merge PDF — When You Need One File Instead of Five</h2>

Sending a project proposal as four separate attachments — the main doc, the budget, the timeline, references — looks disorganized and makes it easy for the recipient to lose track of one. <a href="/merge-pdf">Merging PDFs</a> combines them into a single file in the exact order you choose, so everything arrives as one clean document.

This comes up constantly outside of work too: combining a resume, cover letter, and references into one PDF for a job application, or putting scanned receipts together into a single file for an expense report. Upload the files, drag them into order, merge — the layout and quality of each original page stay untouched.

Good for: job applications, invoice bundles, combining scanned pages into one document.

<h2>Split PDF — When You Only Need Some of the Pages</h2>

The opposite problem: someone sends you a 40-page PDF and you need pages 12 through 15 for a meeting, not the whole thing. Rather than sending the entire file and asking the recipient to "just look at that one section," a <a href="/split-pdf">PDF splitter</a> lets you pull out exactly the pages you need as their own file.

It's also useful for cleanup — removing a signature page you don't want to forward, or breaking a scanned book into individual chapters. You pick the pages (or ranges), and each selection downloads as its own PDF, at full original quality.

Good for: extracting specific pages to forward, removing pages you don't want included, breaking long scans into smaller pieces.

<h2>Convert PDF — When You Need a Different Format Entirely</h2>

Sometimes the problem isn't size or organization — it's that a PDF is the wrong format for what you're doing next. A few conversions come up more than the rest:

- <a href="/pdf-to-word">PDF to Word</a> — when you need to actually edit the text, not just view it
- <a href="/word-to-pdf">Word to PDF</a> — when you're done editing and need a version that won't shift formatting on someone else's computer
- <a href="/pdf-to-jpg">PDF to JPG</a> — when you need an image of a page to drop into a slide deck or a website
- <a href="/jpg-to-pdf">JPG to PDF</a> — when you've got photos or scanned pages and need them as one proper document instead of loose image files

Each of these keeps the layout, fonts, and images intact — the conversion changes the file type, not the content.

<h2>Frequently Asked Questions</h2>

<h2>Do I need to create an account to use these tools?</h2>
No. Every tool works without signing up — upload a file, do the task, download the result.

<h2>Is it safe to upload documents with personal or financial information?</h2>
Yes. Files are transferred over an encrypted connection and automatically deleted from our servers a short time after processing — nothing is kept or shared.

<h2>Will compressing or converting a PDF change how it looks?</h2>
Compression targets image data specifically, so text and layout stay sharp. Conversions (like PDF to Word) do their best to preserve the original formatting, though very complex layouts can shift slightly depending on the target format — that's a limitation of the format itself, not something specific to any one tool.

<h2>Can I use these tools on my phone?</h2>
Yes, all of them work in a mobile browser — no app required.

Four tools, four completely different problems, and none of them need anything installed. Whichever one you need right now, it's a free upload away.


SmallPDF.us Blog

How We Built SmallPDF.us: The Hosting and Stack Behind Our Free PDF Tools

PDF vs Word: Which Format Should You Use and When?

How to Password Protect a PDF (Step-by-Step Guide)

How to Compress a PDF for Email Without Losing Quality

The Ultimate PDF Tools Guide: Compress, Merge, Split & Convert PDFs Online for Free