Performance
Aug 13, 2025
Hosting the Framer site with CloudFront
Introducing how to host a Framer site via Amazon CloudFront, providing detailed guidance on setup and deployment for fast web content delivery. We also explain origin management and connecting custom domains, offering practical information for use.

Uploaded by

Translated by
Contents
Table of Contents
This document was created to help domestic users who are learning Framer overcome difficulties due to the lack of Korean resources. We translated content from the official blog into Korean and added practical information. We hope this provides some help for those using Framer.
What is CloudFront?
CloudFront is a Content Delivery Network (CDN) provided by Amazon.
Framer uses CloudFront by default to deliver assets. Hence, typically, there's no need for separate CloudFront setup, and you should configure it only when more control over the hosting environment is required.
When to configure manually?
When you need to finely control security policies, caching rules, and traffic routing.
When you need to manage multiple origins in an integrated manner.
How to Set Up CloudFront
In your Framer project, go to Settings → Domains.
Add a complimentary Framer subdomain to your site (e.g.,
my-company.framer.website
).

Then, change the Canonical URL option to Advanced in the same menu and enter a custom domain (e.g.,
my-site.com
) before publishing the website.

Note
: You must use a custom Framer subdomain like my-company.framer.website
. Do not use the base domain in the form of <something>.framer.app
.
Create AWS CloudFront Distribution
Go to CloudFront in the AWS Management Console.
Click on Create Distribution.

Enter the Framer subdomain in
Origin Domain
.Important: Use
my-company.framer.website
and not<something>.framer.app

Set the Default Cache Behavior as follows:
Viewer protocol policy
: Redirect HTTP to HTTPSAllowed HTTP methods
: GET, HEAD
(Include OPTIONS, PUT, POST, PATCH, DELETE for password-protected sites)Cache policy
: CachingOptimizedOrigin request policy
: AllViewerExceptHostHeaderResponse headers policy
: SecurityHeadersPolicy

Adjust the options and click on Create distribution.
Once deployment is complete, click the link to verify site access via CloudFront.

Configuring Multiple Origins
For instance, if you want to serve only the /framer-project/
path from the Framer site
URL | Origin |
---|---|
my-site.com | https://my-project.vercel.site |
my-site.com/framer-project | https://my-company.framer.website |
Select Behaviors → Create Behavior from the existing CloudFront distribution.
Enter
/framer-project/*
inPath pattern
.Select Framer project as the origin for that path.
Apply the same cache, protocol, and header policies mentioned earlier.

After saving, wait for deployment completion; you can use two origins in one CloudFront distribution.
Connecting a Domain
To add a custom domain to a CloudFront deployment, use the Alternate Domain Name (CNAME) feature.Note
: If using an apex domain (mysite.com
), Route53 makes it convenient.
This article is a translation and adaptation of Framer’s official blog post, ‘Hosting with Amazon CloudFront’.