Feature Requests

I am furious that you added an unhideable Agent tab! I don’t want any AI slop in my work. I tried it once; it failed like every other AI slop function in other tools. Please add an option to turn off all AI functions in my interface - Especially prominent sidebar in the CMS tab. This was a step backward in every way of using your product. Also, the removal of the CMS button for one click—whose idea was this?! Thanks.

It would be super useful to have support for variables, similar to what Figma offers. Being able to attach specified values to things like padding, gap, or basically anywhere that allows a numerical input would enable a lot of systematic structure that's currently not natively possible. It could work similarly to how text style sizing works, where its possible to define a size based on the breakpoint. Variables could allow for a layer of abstraction in defining consistent system-wide values, such as "padding-large" being set to 128px on desktop and 64px on mobile, for example. This would make updating values across all pages much easier.

Please make the impossible and make plusDarker blend-mode in Framer just like Apple.

Hello Framer team! I hope you're doing well! I finally updated my website to Framer, and I'm pretty excited about it. While making the change, I also switched from Vimeo to Framerate.tv , a new video hosting platform. There's a whole conversation to be had about how many people are leaving Vimeo because of their prices and practices, and a lot of them are finding a new home in Framerate. I started using the Vimeo component, but after switching to Framerate, I realized I had to use the Embed code to bring the videos in. It is working fine for now, but I think it could be better and more seamless if we had a custom Framerate component. This is mainly for seamless loading and optimization, recognizing the correct aspect ratio, and other technical factors that could make this a great fit. Thank you!

Inserting a pre-made footer and a pre-made menu was quick and easy, nowyou have to ask AI agent and run out of credit in two prompts The points of presets components were to prevent spedning time making basic stuff​ fabien • 1m

I found that native Framer Frame image fills can be transferred during the initial page load even when the frames are several viewport heights below the fold. In my project, four service-card image fills located roughly 2,900–7,100px below the top of the page are all requested and transferred before scrolling. The four optimized AVIF transfers total approximately 969 KB: • 211 KB • 325 KB • 346 KB • 87 KB The images are native Framer Frame fills. The rendered images have no lazy-loading hint, and I could not find a supported loading or priority control for the fill. It would be useful if Framer could either automatically defer image fills that are clearly far below the initial viewport, or expose a supported loading priority such as Auto / Eager / Lazy. I would prefer to keep using native Framer fills rather than restructure the design into custom image components or loading code solely to control network behavior. Responsive replicas in my test reused the same URLs, so the issue is not duplicate responsive transfers; it is the initial loading of genuinely below-fold native fills.

I’m using Framer’s native Slideshow component for a homepage hero with four image slides. On a cold page load, all four unique slideshow images are transferred immediately, even though only the first slide is initially visible. In my measured case, the four optimized AVIF images transferred: • 342,675 bytes • 469,173 bytes • 511,599 bytes • 125,509 bytes Total initial slideshow image transfer: 1,448,956 bytes (~1.38 MiB). The slideshow mounts all four slides with loading=auto. Looping also creates additional slide copies, although those reuse the same cached image URLs and do not create additional unique transfers. Framer currently exposes controls for slideshow content, autoplay, interval, transition, clipping, arrows and dots, but I could not find a supported loading/preload control for the slideshow or individual image-filled slide frames. It would be helpful if the native Slideshow could either: • eagerly load only the initially visible slide and intelligently preload the next slide before transition, or • expose a supported loading/preload/priority control for slideshow images. The current behaviour provides seamless transitions, which is valuable, but it can add significant initial page weight, particularly for mobile visitors. I’d prefer to continue using Framer’s native, maintained Slideshow rather than replace it with a custom carousel solely to gain control over image loading.

The Feature: Please add explicit grid line placement controls (grid-column-start / end and grid-row-start / end) for items inside a Grid layout. Currently, Framer only supports column and row spans. The Problem / Friction: Because we cannot choose a specific starting grid line, positioning an item asynchronously (for example, starting exactly at column 2 and ending at column 4) requires a workaround. We have to design and maintain invisible "empty spacer layers" just to push the actual content into the correct track. This creates bloated layer panels, makes responsive breakpoints incredibly tedious to manage, and breaks clean layout logic. The Use Case & Value: Advanced Editorial Layouts: Magazine-style layouts with intentional, asymmetrical white space would become effortless to build. Maintainability: Changing layout positioning across Desktop, Tablet, and Mobile would require zero spacer layer adjustments—just changing the start/end coordinate numbers. Closer to Code: This aligns Framer closer to native CSS Grid capabilities, giving designers the true layout power they expect from the platform.

We always show our clients previews via the URL and it shows the "Made in Framer" badge which is fine. But, our clients are clicking on it and being taken to a page all about AI agents and how this is an AI builder. This is really hurting our business - our clients are thinking we are just pumping our AI websites when they are not. We should be able to choose what landing page the button links to atleast.

Add gradients to the Styles in the Assets panel.