GoHighLevel Media Library: Files, Storage & Speed (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 24 September 2026 · 10 min read

Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.

The GoHighLevel media library is the most neglected part of most sub-accounts I audit, and it is quietly responsible for more slow funnel pages than any automation, tracking script or template choice.

Media Storage looks like a dumping ground, so people treat it like one. This guide covers where files actually live, the limits HighLevel publishes, how your image URLs get rewritten on the way to the browser, and the housekeeping routine that keeps a client account usable two years after you build it.

Where GoHighLevel media storage actually lives — and why it matters

Media Storage sits in the left sidebar of a sub-account, and every file you upload belongs to that location. There is no shared agency-wide asset pool that silently follows you into new builds.

Treat one sub-account as your template library and upload finished brand assets there first, then copy outward. It costs nothing and it gives you a single source of truth when a client asks which logo is current.

Agency assets versus client assets

If handover is on your roadmap, read it alongside our guide to a clean GoHighLevel client offboarding and data export process — media is one of the assets people forget to account for.

The folder structure and naming convention that survives a team

HighLevel supports up to three levels of nested folders, and folder uploads handle up to 1,000 files at a time. Three levels is enough for any sensible structure and not enough for a bad one, which is a useful constraint.

The structure I install in every account we build:

• 01-brand — logos, favicons, brand colours reference, fonts
• 02-funnels — one subfolder per funnel, named for the offer
• 03-email — headers, signatures, inline graphics
• 04-social — Social Planner-sized exports only
• 05-blog — cover images and in-article graphics
• 06-documents — PDFs, proposals, lead magnets
• 99-archive — superseded assets nobody may use

Filenames matter more than folders because filenames travel into the public URL. Use lowercase, hyphens and meaning: acme-plumbing-hero-emergency-callout-1600.webp beats Final_v3_NEW(2).png in every way that counts.

What you can upload: HighLevel media storage file types and real limits

HighLevel accepts a far wider range of formats than most people realise — images, video, audio, documents, fonts, vCards, and an expanded set covering RAW photography, CAD, design source files and archives.

The limits that trip people up are not the format list, they are the per-product caps — the same file can be legal in the Media Library and rejected by Social Planner.

Source: HighLevel's Media Storage file types, limits and advanced features documentation. Separately, the email composer accepts up to 20MB of direct attachments before it converts the file into a Media Library link instead.

How HighLevel serves your files: filesafe.space and the transform wrapper

Files you upload land on assets.cdn.filesafe.space, under a path that includes your location ID and a generated file ID. That is the raw origin URL for the asset.

What actually gets served to a visitor on most pages is a wrapped URL beginning images.leadconnectorhq.com, with transform parameters baked into the path — typically f_webp, q_80 and r_1200.

Read that string literally: format WebP, quality 80, resized to a maximum width of 1200 pixels. HighLevel is re-encoding your image on delivery, and those are the platform defaults reported on HighLevel's own ideas board.

The practical implication is the opposite of what most designers assume. Because the wrapper caps width, exporting above roughly 1600px wide achieves nothing visible on standard funnel layouts.

It also means WebP is doing real work for you by default. Google's own figures put WebP lossy images at 25–34% smaller than comparable JPEG at equivalent quality, and WebP lossless at 26% smaller than PNG.

Why oversized hero images are the number one cause of slow GHL file storage pages

Across the audits we run, an unoptimised hero image is the single most common reason a HighLevel funnel fails its speed check. It is almost always the Largest Contentful Paint element too, which means it is the thing Google times.

Google's guidance in web.dev's Largest Contentful Paint documentation is that a good LCP is 2.5 seconds or less, measured at the 75th percentile of page loads across mobile and desktop.

For scale: the HTTP Archive Web Almanac 2025 put the median mobile page at 2,164 KB total, with 911 KB of that being images. A single 3MB uncompressed hero puts your page well past the median before a single font or script loads.

If your pages are already slow, work through our full breakdown of fixing slow GoHighLevel funnel pages — media weight is step one, but it is not the only culprit.

Correct dimensions and compression targets before you upload

Compress before upload, not after. The delivery wrapper is a safety net, not a workflow — and it cannot recover a file you exported at the wrong dimensions.

Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.

Alt text, filenames and the SEO half of HighLevel media storage

Google's Image SEO best practices documentation asks for two things the media library makes easy to get wrong: descriptive filenames and useful alt text.

Google's example is blunt — my-new-black-kitten.jpg is better than IMG00023.JPG. Rename the file before upload, because you cannot rewrite the URL afterwards without re-uploading.

Alt text describes the image in the context of the page; it is not a keyword slot. Google explicitly warns that keyword-stuffed alt text reads as spam.

Using media across funnels, emails, the blog and Social Planner

Each surface pulls from the same Media Storage but applies its own rules, and knowing them saves a lot of failed uploads.

• Funnels and websites — 100MB image cap, but the delivery wrapper resizes to 1200px, so export to spec
• Email — attachments over 20MB become Media Library links; see our HighLevel email builder walkthrough for layout specifics
• Blog — cover images are what social platforms scrape, so name and size them deliberately
• Social Planner — the tightest caps at 10MB for images and 1GB for video; our Social Planner scheduling guide covers the posting workflow
• Memberships and courses — 5GB video ceiling, the most generous on the platform

What happens to media when a snapshot loads or a sub-account transfers

This is where agencies get caught. Snapshots are built around funnels, workflows, calendars and pipelines — the media library is not a first-class citizen in that payload.

HighLevel's own ideas board carries a long-standing, still-open request to add media folders and images to snapshots, and users report assets arriving unfoldered rather than in their original structure. Plan your builds on the assumption that folder organisation does not survive a snapshot load.

Practically: re-upload and re-file brand assets during onboarding, then verify hero images render on every page after a load. Our guide to pushing snapshot updates to live sub-accounts covers the wider verification checklist.

Sub-account transfers are different: the location moves intact and its media goes with it — which is precisely why agency artwork should never have been in there.

A quarterly housekeeping routine for GHL file storage

• Open the media usage breakdown and note which module is growing
• Sort by size and inspect anything over 1MB that is not a video
• Re-export and replace oversized heroes, then update the funnel reference
• Move superseded assets to 99-archive rather than deleting them outright
• Empty Trash deliberately, remembering the 30-day retention window
• Spot-check five live pages for missing or broken images after any snapshot activity

Pair it with your sub-account backup and restore routine so the two run in the same session each quarter.

Common mistakes to avoid

• Uploading straight from a camera or stock site with no resize or compression step
• Exporting above 1600px wide when the delivery wrapper caps images at 1200px anyway
• Leaving filenames as IMG_4471.png, which then becomes part of a permanent public URL
• Storing agency-owned artwork inside client sub-accounts that may later be transferred
• Assuming a snapshot will carry your media folder structure across intact
• Pasting a private, time-limited file link into documentation as if it were permanent

If you want your HighLevel media library audited, restructured and your slow funnel pages fixed properly, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.

Frequently asked questions

Is GoHighLevel media storage unlimited?

HighLevel's published documentation specifies per-file and per-product upload limits but does not state a total account storage allowance. It does provide a usage modal showing consumption by module and file type. Treat storage as generous rather than guaranteed-unlimited.

What is the maximum image size I can upload to the media library?

HighLevel's documentation lists 100MB per image file in the Media Library and in Sites & Funnels, 50MB in Courses, and 10MB in Social Planner. Those are hard caps, not targets. In practice you should be exporting funnel images under 200KB.

Why do my images look compressed or pixelated after publishing?

HighLevel serves images through the images.leadconnectorhq.com wrapper, which by default converts to WebP at quality 80 and caps width at 1200 pixels. Preview views can look sharper than the published page for that reason. Export at the right dimensions so the re-encode has less work to do.

Where are GoHighLevel media files actually hosted?

Uploaded files sit on assets.cdn.filesafe.space under a path containing your location ID, and are typically delivered through the LeadConnector image transform domain. Both are HighLevel-controlled hosts, and branded media domains remain a requested feature rather than a standard one.

Do snapshots include the media library?

Not reliably, and not with folder structure intact. HighLevel's ideas board still carries an open request to include media folders and images in snapshots, and agencies report assets arriving unorganised. Build your onboarding process on the assumption that you will re-upload and re-file brand assets manually.

How long do deleted media files stay recoverable?

Deleted files move to Trash and are retained for 30 days before permanent removal, according to HighLevel's Media Storage documentation. That gives you a genuine recovery window if someone removes a live asset by mistake. It is not a substitute for keeping master files outside the platform.

Does image optimisation actually affect my Google rankings?

Indirectly but meaningfully. Images are usually the Largest Contentful Paint element, and web.dev defines a good LCP as 2.5 seconds or less at the 75th percentile. Descriptive filenames and contextual alt text also help Google understand and surface your images, per Google's Image SEO documentation.

Should I host images outside HighLevel instead?

For most agencies, no — the built-in storage is convenient and the WebP delivery is genuinely useful. External hosting is worth considering only when you need image quality above the default 1200px, quality-80 treatment, such as high-detail product photography.

Related Articles on HL Growth Partner

Speed, pages and builders

• Diagnosing page speed problems in HighLevel
• Website builder versus funnels: which to use
• Content AI setup and pricing explained

Account hygiene and handover

• Agency security, 2FA and role permissions
• Importing contacts and mapping CSV fields
• Exporting client data at the end of an engagement

Where your media gets used

• Setting up memberships and courses
• Ecommerce store setup and transaction fees