Serve an SVG background with the HTTP response header Content-Type: image/svg+xml. Set its Cache-Control policy based on how the asset is deployed: long freshness can work when changed files get new URLs, while a stable URL calls for shorter freshness or a reliable revalidation or purge process. There is no universal cache lifetime for SVG files.
Set the MIME type on the SVG response
The registered media type for SVG is image/svg+xml. The W3C registration identifies .svg as the normal file extension and allows an optional charset parameter; it does not require one. See the W3C SVG media-type registration.
For a CSS background, the stylesheet references the SVG URL, and the server or serving layer returns that file and its response headers. Set Content-Type on the SVG response—not on the CSS file. A filename ending in .svg does not substitute for the correct response header: browsers use the returned MIME type to determine how to process a resource. MDN lists image/svg+xml as an image type and explains the role of response MIME types in its MIME types guide.
SVG is valid in CSS background-image. When loaded as an image, browser security restrictions can prevent scripts from running and external resources from loading; that behavior differs from embedding an SVG as a document. See MDN’s background-image reference.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Choose Cache-Control for your deployment model
Cache-Control: max-age=N sets a freshness lifetime of N seconds. A cache may reuse the response while it is fresh. After the response’s age exceeds that lifetime, it is stale and may need validation or replacement. HTTP can heuristically cache some responses even when no explicit Cache-Control is present, so an explicit policy gives more predictable behavior. See MDN’s Cache-Control reference.
Pick a policy according to whether the URL changes when the SVG changes. These are deployment strategies, not SVG-specific standards:
| Deployment approach | Cache policy direction | Main trade-off |
|---|---|---|
| Change the asset URL whenever its contents change | A longer freshness lifetime may fit because a new URL identifies the updated asset. | Visitors can keep using the old URL until the page or stylesheet points to the new one. |
| Keep the same URL while replacing the file | Use a shorter freshness lifetime, or arrange revalidation or cache invalidation when deploying updates. | Short freshness can prompt more frequent checks; without effective validation or purging, a changed file may not appear promptly. |
The appropriate duration depends on how often the graphic changes, how quickly visitors must see an update, and how reliably your deployment can change URLs or invalidate caches. The HTTP specifications do not prescribe one correct max-age for SVG backgrounds.
When Expires is also set
Expires specifies an absolute expiration date, while max-age specifies an elapsed lifetime. If both are present, max-age takes precedence. See MDN’s Expires reference. Avoid relying on conflicting values; configure the intended freshness policy explicitly.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Check the response when a background fails or stays stale
-
Request the SVG URL directly and inspect the response status,
Content-Type, andCache-Control. Confirm that the type isimage/svg+xml. -
Check that the CSS
background-imageURL points to the intended deployed SVG, rather than an old path or a different asset. -
If the public response differs from the origin response, investigate the CDN or reverse-proxy cache policy and its purge or invalidation behavior.
-
After changing configuration or deploying a replacement, test again. Separate browser-cache behavior from shared-cache behavior when diagnosing the result.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Account for a CDN or reverse proxy
A CDN or reverse proxy is a managed cache. It may follow response headers, apply service-specific rules, or expose additional controls and headers. The origin’s Cache-Control value alone may not describe what visitors receive. Check the documentation for the specific service and verify the response at the public URL as well as, where possible, at the origin. MDN describes shared-cache behavior in its HTTP caching guide and Age header reference.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
