Vercel Seems an Attractive Option – Until You Hit the Media Library

Getting your Trinity Audio player ready...
Reading Time: 3 minutes
AI‑native tools like Google Stitch MCP and Antigravity make it feel effortless to generate a modern, responsive, beautifully structured website. You describe the vibe, the AI generates the layout, and Vercel deploys it instantly.

But once the novelty wears off, a deeper question emerges:

What happens when you try to migrate a real WordPress site — with years of posts, images, PDFs, and legacy URLs — into this new world?

This is where the fantasy of “just vibe code it” collides with the operational reality of a mature content site. And it’s exactly where many users quietly give up.


Redirects

A WordPress sitemap is a list of URLs — not a redirect map. But it is the perfect starting point.

A practical migration workflow looks like this:

  1. Export all URLs from sitemap.xml
  2. Map each old URL to its new clean URL
  3. Convert the mapping into Vercel redirect rules
  4. Insert them into vercel.json
  5. Test everything on a preview deployment

WordPress URLs often include:

  • date folders
  • category folders
  • attachment pages
  • querystring permalinks
  • image paths
  • PDF downloads

A single post might have multiple historical URLs that all need to resolve to the new canonical slug. WordPress plugins handle this automatically. Vercel does not.

For a site with 200 posts, you might end up with hundreds of redirect rules unless you use pattern‑based redirects. It’s doable — but it’s not “fun.”


Media

This is the moment where most users hit the wall.

WordPress stores media like this:

/wp-content/uploads/2020/09/image.jpg

And it generates:

  • multiple sizes
  • WebP variants
  • attachment pages
  • metadata
  • plugin‑generated thumbnails

A static site has none of that machinery.

Option A: Migrate everything

  • Download the entire uploads folder
  • Upload it to your new project
  • Rewrite every image URL
  • Add redirects for old media paths

Clean long‑term, but time‑consuming and easy to break.

Option B: Keep WordPress for media

The most common real‑world solution:

  • Move WordPress to media.example.com
  • Disable everything except uploads
  • Rewrite image URLs to that subdomain

No media migration. No broken images. Minimal stress.

Option C: Use a storage bucket

  • Export uploads
  • Upload to S3/R2/etc.
  • Serve via CDN
  • Rewrite URLs

Great for developers, too complex for most beginners.

Where people quit

  • They see 10,000 files in /uploads/
  • They break image paths and don’t know why
  • PDFs start 404ing
  • Google Search Console fills with missing media
  • They realize attachment pages also need redirects

Responsive

A Vercel site is responsive because the framework is responsive, not because Vercel does anything special.

Most AI‑generated sites use:

  • Tailwind CSS (utility‑first responsive classes)
  • Next.js <Image /> for responsive images
  • flexbox and grid layouts
  • mobile‑first breakpoints

This is why they look clean on mobile.

The catch: if you want to adjust responsiveness, you must edit the code. There is no Elementor panel, no theme customizer, no drag‑and‑drop mobile view.


Tailwind

Tailwind CSS is not a SaaS product. It’s:

  • a CSS methodology
  • an open‑source framework
  • a design system baked into your code

You don’t sign up, log in, or pay. But you do need to understand utility classes if you want to tweak layouts manually.


Drop-off points

Non‑technical users tend to abandon the migration at very specific moments:

  • They download the uploads folder and panic at the file count
  • They break image URLs and can’t fix them
  • They can’t see how to manage 200+ redirects
  • They don’t understand Tailwind classes
  • They can’t adjust mobile layouts without touching code
  • They hit Vercel’s image optimization limits
  • They realize PDFs and attachment pages also need redirects

At that point, many quietly return to WordPress — not because the new stack is bad, but because WordPress hides a decade of complexity behind plugins and UI.


Should you move?

If you’re building a new site from scratch, the AI‑native workflow is a joy.

If you’re migrating a mature WordPress site, the work is real.

A static Vercel site gives you:

  • speed
  • security
  • modern design
  • clean code
  • no plugin bloat

WordPress gives you:

  • effortless media management
  • automatic redirects (via plugins)
  • automatic image handling
  • visual editing
  • SEO plugins that automate the boring parts

The right choice isn’t about hype. It’s about your tolerance for manual work — especially once you hit the media library.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Mastodon