A portfolio has one job: show the work and make contact easy. WordPress can do that with a theme, a media library, and a form. Static HTML can do that with fewer moving parts. The hosting decision starts with whether you need the CMS — not with which host has the prettiest “portfolio” landing page.

WPHost hosts WordPress on PHP 8.4 + MySQL when you choose the CMS. If your portfolio is already a folder of HTML/CSS/JS with no PHP, a static host is simpler. Pick on purpose.

When WordPress is the right portfolio engine

Choose WordPress if you:

  • Want non-developers (you, a future you, an assistant) to add case studies in wp-admin
  • Need a blog beside the work — blog hosting
  • Rely on a theme/ecosystem you already know
  • Expect plugins for forms, SEO, or light ecommerce of prints — Woo honesty

Accept the costs: updates in wp-admin (we do not auto-update), a database to back up, and plugin restraint.

When you already have HTML

If the portfolio is exported from a design tool or hand-coded and rarely changes, shipping static files avoids MySQL entirely. You will not fight cache plugins or core updates. WPHost can run PHP sites, but forcing WordPress onto a finished static portfolio is ceremony for its own sake. Be honest in kickoff meetings — especially agencies and freelancers billing rebuilds — agencies, freelancers.

Hosting shape when you do choose WordPress

  1. Create a PHP site; upload WordPress zip (no one-click installer today).
  2. Provision MySQL; configure wp-config.php — setup.
  3. Install on preview HTTPS — first host.
  4. Theme that emphasizes galleries/case studies without shipping 20 demo plugins.
  5. Backup plugin for DB + files — SSL and backups.
  6. Custom domain; set https siteurl/home — custom domain.

Starter $9 (1 site, 2 GB) fits many text-and-thumbnail portfolios. Image-heavy work climbs storage: Pro 10 GB, Scale 30 GB, Business 100 GB — image-heavy. Photographers and designers get specialized notes below.

Media is the portfolio

Portfolios fail when images are enormous. Resize for the grid; link to case study pages for detail. Offload if needed. We provide no built-in CDN; Cloudflare optional.

Do not treat the media library as cold storage for every RAW file you have ever shot. Keep masters elsewhere — photographers.

Page builders versus themes

Builders are plugins you install — they are not “the host.” They help some designers ship layouts faster and hurt others with bloat — designers. For a portfolio, a well-made niche theme can beat a generic builder stack. Staging on Pro+ is where you find out — staging.

Contact forms and email

WPHost does not include email hosting. Forms need SMTP to a real provider. “Portfolio contact broken” after migration is usually mail, not DNS — transfer.

Security and updates without a team

Solo portfolios still get scanned. Fewer plugins, 2FA, monthly updates — secure. Deploy history helps if a theme upload goes wrong; it will not restore deleted case-study posts without a DB backup.

Performance expectations

PHP 8.4 + compressed images + minimal plugins is enough for most portfolios. We will not claim 400% — fast. Viral Behance-level traffic spikes are rare; if you publish a famous case study, cache helps — high traffic.

What is not included (same honesty)

No cPanel, no Softaculous, no auto plugin updates, no nonprofit coupon, no long trial (~1 day), no built-in CDN, GitHub per-person if you use it. Managed runtime yes; managed design career no — managed.

Decision flowchart in words

  • Need wp-admin editing → WordPress on WPHost
  • Already static & rarely edited → static hosting
  • Heavy client proofing workflows → read photographer guide; evaluate plugins honestly
  • Selling prints → small Woo possible; no commerce SLA

Launch mindset once built: how to launch.

Case study pages that do not melt phones

A portfolio case study often wants a big hero, a grid, and a process narrative. Budget weight:

  • One strong hero at web width, not a 6000px billboard
  • Process images as a gallery with lazy-load
  • Optional video via Vimeo/YouTube embed rather than a 200 MB self-hosted mp4
  • Related work as thumbnails linking to other case studies

PHP 8.4 will not save an unoptimized case study template — fast. If every project page is a unique page-builder snowflake, expect longer update tests on staging.

Domains and personal brands

Freelancers often launch on name.design while keeping email at Google. Attach the domain after content is ready; keep MX untouched — transfer. Avoid launching on a temporary preview hostname in your pitch deck if the custom domain will change all screenshots a week later.

Multi-lingual portfolios

Multilingual plugins add database weight and cache complexity. They can run. Test language switchers logged-out and logged-in; confirm media alt text strategy. We do not provide a translation SLA — only the PHP/MySQL host.

Migrating a portfolio from Squarespace or .com

Expect a rebuild more often than a perfect import. Move what matters: images (resized), project copy, and SEO URLs with redirects. Hosting is ready before the writing is — migrate when you have a real WordPress export; otherwise treat it as a new install — how to host.

Analytics without wrecking the aesthetic

Portfolios die under five tracking scripts. Pick one analytics approach or none. Cookie banners, if required, should not obscure the first project image. Performance budget is part of design craft — fast.

Passworded “client only” pages are fine for works-in-progress; for serious proofing workflows, read photographers before inventing a fragile members plugin stack.

Contact CTAs that work after launch

A beautiful portfolio with a dead form is a paperweight. SMTP must be configured before you print business cards with the URL — how to launch. Keep the ask simple: email or a short brief form. Calendly embeds are fine; five marketing pixels are not.

Installing a portfolio the long way (the honest way)

Create a PHP site, upload a WordPress zip with index.php at the document root, provision MySQL, and write the four DB defines into wp-config.php. Generate salts. Run the installer on the HTTPS preview. Pick a non-admin username. There is no one-click shortcut on WPHost — and that is fine for a portfolio you intend to keep clean.

Compress project images before the media library becomes a junk drawer. Deploy history rolls back theme files; it does not replace a database-aware backup of case-study copy. When you attach a custom domain, wait for DNS verification before chasing padlock anxiety — custom domain.

Client work versus your own brand site

Your portfolio on Starter ($9) should not become an accidental host for client WordPress installs. Isolate clients on additional site slots (Pro $30 and up) with their own databases. Staging on Pro+ needs a DB copy when you rehearse a redesign against real case studies — staging. We do not auto-update portfolio plugins; update after backups.

FAQ

Can I host a portfolio on Starter?

Yes if one site and ~2 GB of web-sized images suffice. Upgrade when galleries grow.

Should my portfolio be a WordPress.com site instead?

Only if you accept .com constraints. Self-hosted .org on WPHost is for plugin freedom and ownership — beginners .org vs .com.

Do you provide portfolio themes?

No theme marketplace. Bring your own from wordpress.org or a vendor.

Can I migrate a static site into WordPress on WPHost?

You would rebuild content into WordPress (or use import tools). Hosting does not convert HTML to CMS automatically.

Is staging useful for portfolios?

Yes when testing builders, gallery plugins, or cache. Pro+.