How to build a monthly/yearly pricing toggle in Framer
Build a monthly/yearly pricing switch in Framer with one component, two variants and a tap interaction, plus tips on showing savings clearly.

Almost every SaaS landing page has the same small control above the pricing cards: a switch between monthly and yearly billing. It looks trivial, but it is one of the most clicked elements on the page, and when it is built badly the prices jump, the layout shifts, or the yearly discount is hidden in small print nobody reads.
In this guide we build the toggle in Framer the way we do it on client projects: with one component, a few variants, and tap interactions. No code components, no overrides. You will end up with a pricing section you can reuse, edit in one place, and hand off to a client without worrying that they will break it.
Decide what the toggle actually changes
Before opening Framer, write down every piece of content that differs between the two states. On most pricing pages that list is longer than people expect:
- The price on each card
- The billing note under the price ("per month" vs "per month, billed yearly")
- A savings badge on the yearly side ("2 months free" or "Save 20%")
- Sometimes the button label or the link it points to, if checkout differs per plan
Everything on this list must live inside the same component as the switch. That is the single most important decision in this build, and the next section explains why.
Why the switch and the cards belong in one component
A Framer interaction on a component instance can change that component's own variant. It cannot reach across the canvas and change a different, unrelated component. So if you build the switch as one component and the pricing cards as another, tapping the switch has no clean way to update the prices.
The reliable pattern is to make the whole pricing block one component: the switch on top, the cards below. When the visitor taps the switch, the entire block changes from the Monthly variant to the Yearly variant, and every price, note and badge updates together. The cards themselves can still be nested components, which keeps them easy to maintain.
Build the card once, with properties
Start with a single pricing card as its own component. Give it component properties (variables) for the parts that change: plan name, price, billing note, feature list and button label. Add a boolean property for the savings badge so you can show or hide it per instance.
A few details make the card hold up in real use:
- Use a stack with fixed padding, so a longer price like "$1,290" pushes content down instead of overlapping it.
- Set the price text to a tabular or monospaced figure style if your font supports it, so the numbers do not shift width when they change.
- Keep the billing note on its own line. Squeezing it next to the price causes wrapping on mobile.
Create the Monthly and Yearly variants
Now build the parent pricing component. Place the switch at the top and three card instances below it in a horizontal stack. This first state is your Monthly variant. Fill in the monthly prices and notes, and hide the savings badges.
Duplicate it as a second variant and name it Yearly. In this variant, change the card instances' property values to the yearly prices, switch the billing note, and turn the badge on. Move the switch knob to the other side and change its fill so the active state is obvious.
Because both variants share the same layers, Framer can animate between them. Keep the layer names and structure identical in both; if a layer exists in only one variant, it will pop in rather than transition.
Wire up the interaction
Select the switch layer in the Monthly variant and add a tap interaction that changes the component to the Yearly variant. Do the same in the Yearly variant, pointing back to Monthly. That is the whole mechanism.
Then tune the transition. A short ease or a gentle spring works well; long, bouncy animations make prices feel unstable, which is the opposite of what you want on a page where people are deciding to pay. Test it a few times in the preview and watch for anything that slides around unexpectedly.
If a price visibly "travels" across the card during the transition, the text layer is changing size. Fix the width or alignment of the text box rather than fighting it with animation settings.
Show the yearly saving clearly
The toggle exists to sell the yearly plan, so make the benefit easy to read. Put a short badge next to the "Yearly" label itself, not only on the cards, so visitors see the saving before they tap. State it in concrete terms. "Save $48 a year" is easier to judge than "Save 20%", and "2 months free" is easier still if your maths supports it.
Also decide how to present the yearly price. The common and honest approach is to show the monthly equivalent in large type with a note underneath such as "$290 billed yearly". Showing only the large annual total makes the plan look more expensive at a glance; showing only the monthly equivalent without the billed amount feels like hiding something.
Make it work on mobile and for keyboard users
On smaller breakpoints, switch the card stack to vertical and check that the switch stays visible above the first card. If visitors have to scroll past three tall cards to find out the toggle exists, most will never use it.
A few accessibility checks are worth the five minutes:
- Label both sides of the switch with text ("Monthly" and "Yearly"), not just colour, so the current state is readable without relying on hue.
- Make the tap target at least 44 px tall, including some padding around the knob.
- Check contrast for the inactive label; light grey on white is a common failure here.
- Tab through the page in the preview and confirm you can reach the switch and the buttons in a sensible order.
Choose a sensible default and test it
Which state the page loads in is a business decision, not a design one. Defaulting to Yearly puts the lower monthly equivalent in front of people and can lift annual sign-ups; defaulting to Monthly feels more transparent to visitors who are still unsure. Set the default by choosing which variant the instance on the page uses.
If you are not sure, test it. Framer's built-in A/B testing lets you run two versions of a page or section and compare results, so you can try a Yearly default against a Monthly default and look at the clicks on the plan buttons rather than guessing. Give the test enough traffic and time before you call it.
Hand it off without surprises
Before you hand the site to a client, rename the variants and properties in plain language ("Monthly", "Yearly", "Price", "Billing note") and leave a short note on the canvas explaining that prices must be changed in both variants. A classic support request on pricing sections is "I updated the price and it changed back", which is almost always someone editing one variant and forgetting the other.
If prices change often, consider moving them into a CMS collection or a single source of component properties so there is only one place to edit. The fewer places a number lives, the fewer chances it has to be wrong.
A good pricing toggle comes down to three decisions: keep the switch and the cards in one component, make the two variants structurally identical, and state the yearly saving in plain numbers. Get those right and the rest is polish. Build it once as a reusable section, and the next pricing page you design will take minutes instead of an afternoon.


