How to Share a PDF Catalog with Customers the Right Way

You probably have the catalog finished in InDesign, the sales team wants it out today, and someone is still asking whether to email the PDF or post it somewhere. Send it as a browser link, not as an attachment. That's the cleanest way to share a PDF catalog with customers when the file is image-heavy, needs updates, and has to open well on phones, tablets, and laptops.

If you want the short version, do this: export a clean PDF, upload it to a browser-viewable link, set your access rules, generate a QR code for print, and keep the same URL when the file changes. That turns one catalog into a usable channel instead of a one-time file drop.

Why a Catalog Link Beats an Email Attachment

Export the catalog once, then publish the PDF through a browser link. That's the routine worth learning, because email attachments are the wrong place for a catalog that carries product photos, layouts, and pricing pages.

Microsoft notes that many email providers cap attachments at roughly 20 to 25 MB, and email encoding reduces the usable file content even further, so a file that looks like it fits can still be too large in practice, especially for image-rich product catalogs, seasonal brochures, restaurant menus, and sales decks. A browser link avoids that mess and gives customers a cleaner way to open the same catalog on a phone, tablet, or desktop without needing a separate PDF app. Microsoft's guidance on large file delivery is the right reference point here, and the browser-link approach is exactly what NanoPIM catalog examples help illustrate in a practical way.

Practical rule: if the catalog matters enough to print or send to buyers, don't bury it inside a mailbox attachment.

The bigger win is control. A catalog link can stay the same while the underlying PDF is replaced, so your email campaign, sales message, social post, and printed handout can all point to one current edition. That matters when prices change, stock shifts, or a seasonal line gets refreshed.

Use the link as the canonical destination, not as a one-off share method. Then every channel, email, DMs, printed flyers, and sales follow-up, can point to the same live file instead of scattering outdated copies across inboxes.

Exporting the Catalog From Adobe InDesign

Start in File > Export, choose Adobe PDF, and name the file for the customer-facing version, not your internal working draft. If you've only used the default export settings before, most catalog mistakes start here.

In the Adobe PDF Presets panel, pick a preset that matches the final use, not the prettiest label. For broad customer viewing, a modern compatibility setting matters more than nostalgia for old print workflows, so keep the PDF readable in current browsers and common viewers. If the catalog may also be printed later, preserve bleed and marks during export so the file can serve both jobs without a second rebuild.

The settings that keep the file sane

Use the export options that protect readability and file size. If the catalog is full of photography, compression is not optional, it's the difference between a browser-friendly PDF and a bloated one that clients won't wait for.

• Compatibility: choose a setting that supports broad viewer access.
• Bleeds and marks: keep them on only when the catalog needs print production.
• Image compression: reduce oversized image weight before the PDF leaves InDesign.
• Links and text: keep text live where possible, don't flatten everything into images.
• File naming: use a versioned name so the production team knows what was exported.

If you're exporting a catalog that originated from product photography shot on phones, a separate cleanup step helps. For that kind of source material, iPhone HEIC to PDF methods are useful context when you're moving assets into a production pipeline before layout, not after.

Keep the design file print-ready, but don't let the PDF inherit every print-only habit. Browser delivery needs restraint.

The mistake I see most often is over-exporting. Designers leave huge images, extra marks, and old print settings turned on because the file looks fine on their workstation. The customer opens it on a slow connection and pays for all that extra weight.

Choosing Between Print-Ready and Web-Ready PDF Presets

Pick the preset based on what the catalog does in practice. If it is going to a printer, you need one setup. If it is going straight to customer devices, you need another. Mixing those two jobs into one sloppy export is how catalogs become hard to open, hard to print, or both.

For a print-ready version, keep the file production-friendly. For a web-ready version, strip out everything that doesn't help the customer read it quickly. That distinction matters more than chasing a perfect one-file-to-rule-them-all export.

If the catalog is going into a showroom binder, mailer, or sales packet, print settings win. If it's being sent to customers who will tap it open from email, chat, or a QR scan, web settings win. The wrong preset doesn't just waste time, it can make the file awkward in the browser and slow on mobile data.

For a merchandising system where color matters, use a resource like merchandising color combinations to keep the visual direction intentional before you export, not after the PDF is already circulating.

Rule of thumb: print-ready files protect output on paper, web-ready files protect attention on screens.

If your business needs both, export both. Give the printer the heavier version and give customers the lighter one. Don't ask one PDF to do two jobs badly.

Uploading the PDF and Creating a LinkShip Share Link

Upload the exported PDF to a browser-viewable share link, then treat that link as the catalog's public address. In LinkShip, the PDF to Link flow is built for that, and the usual path is straightforward, upload the file, generate the share URL, then decide how customers should access it. The cleanest walkthrough is also covered in this PDF upload guide.

What to set before you send it

Don't stop at upload. Set the customer-facing details while the file is still fresh in your mind, because that's what controls how usable the catalog is once it leaves your desk.

• Custom slug: use a clean, readable URL instead of a random string.
• Password protection: use it for dealer pricing or restricted catalogs.
• Expiry date: set it for seasonal catalogs or time-limited promotions.
• View-count caps: use them when a confidential launch needs tighter control.
• File replacement: swap the PDF behind the same URL when the catalog changes.

That last point is the reason to use a link-based workflow. The URL stays stable, but the document behind it can be replaced. Printed QR codes keep working, saved bookmarks don't break, and you avoid sending outdated copies to customers who already clicked the first version.

If you manage product sheets, pricing books, or seasonal assortments, stop thinking in terms of attachments. Think in terms of one public catalog address that can be updated without starting over.

Bridging Print and Digital With Tracked QR Codes

A QR code should point to the short catalog URL, not carry the PDF itself. That keeps the printed code small, easier to scan, and easier to maintain when the underlying catalog changes. If you're putting it on packaging, menus, brochures, or a counter card, the code is just the doorway, the link is the destination.

For printed material, choose stronger error correction when the code might get scratched, folded, or marked. DENSO WAVE explains that QR codes support multiple error-correction levels, and the practical choice is simple, use enough resilience for the physical surface you're printing on without making the code unnecessarily cramped. The official QR error-correction guidance from DENSO WAVE is worth respecting, especially when a code will sit on a restaurant table tent or a trade-show handout.

The other piece is measurement. QR scans should be tracked separately from ordinary link clicks so you can tell whether a table tent, packaging insert, or brochure is getting used. LinkShip's QR workflow supports that separation, which is the only sensible way to judge print performance alongside email and social traffic. For setup details, the QR code creation guide is the practical companion to the share link.

Print a short fallback URL beside the QR code. People still need a manual option when a camera won't cooperate.

Do not print a QR code before the destination is final. Test it from a few phones, at the actual size, in the actual light, and with the actual distance your customer will scan from. A code that looks fine on your monitor can fail on glossy stock or in a dim dining room.

Mobile Reading and Accessibility Before You Hit Publish

A catalog can load quickly and still fail on a customer's phone. Tiny type, image-heavy pages, and a confusing reading order interrupt browsing after the share link has done its job. Build the document around the reading experience first, and treat the layout as its container.

What must be true before customers see it

North Carolina's digital accessibility guidance recommends document-structure tags, checked reading order, an accessibility checker, screen-reader testing, and saved corrections. Adobe explains the purpose of PDF tags clearly: the tag tree tells assistive technology how to interpret the document.

• Searchable text: use live text instead of scanned pages wherever possible.
• Bookmarks: give longer catalogs a practical way to move beyond continuous scrolling.
• Heading structure: arrange product groups, categories, and ordering details in a logical sequence.
• Alt text: describe useful images, especially when product details carry sales information.
• Image compression: keep photos clear while preventing slow loading and excessive mobile zooming.

For longer PDFs, bookmarks deserve deliberate production time. The HHS PDF-tagging guide says PDFs with more than 9 pages need bookmarks and recommends adding them after heading structure and tagging are complete. Follow that sequence so buyers can move from categories to specific product groups without searching page by page.

After upload, review the live file on a phone rather than relying on the InDesign document. Open the first pages, test every product link, confirm the text remains readable, and watch for points where browsing slows down. If you want the catalog on your own page instead of a standalone link, see how to embed a PDF document in HTML. Check that page on the same mobile devices your customers use, because browser rendering can expose problems that desktop review misses.

Your Repeatable Catalog Sharing Runbook

Use the same production sequence every time, and the catalog stops feeling like a one-off project. Export from InDesign with the right PDF preset, upload the file to a browser link, set the access rules and custom slug, then generate the QR code for print. That's the whole workflow, and it's enough for a small business, restaurant, or sales team that wants one catalog system instead of a pile of disconnected files.

The live-channel mindset matters here. The PDF is not the final product, the URL is. Once that clicks, the rest of the workflow gets simpler, because every new edition can replace the old one without breaking the places where customers already found it.

Review the catalog the week after launch, not months later. Check which channel sent visitors, which pages held attention, and where people dropped off before the call to action. If a specific page gets ignored, it usually means the layout is confusing, the image is too heavy, or the product path is buried.

Use this runbook every time:

1. Export the file from InDesign with the right preset for print or web.
2. Upload it to a share link instead of attaching it to email.
3. Set the controls, slug, password, expiry, or view cap, based on the catalog's audience.
4. Create the QR code only after the destination is final.
5. Track the response through scans, visits, and page-level engagement.

If you want one place to keep that process tight, LinkShip gives you browser-based PDF sharing, replacement of the file behind the same URL, access controls, and QR tracking in one workflow. Set up your next catalog there, then run it like a live channel instead of a static attachment.