Feature Requests

Ability to render/define LaTeX formulas and see rendered math in CMS items. Both inline in Rich Text and a separate LaTeX insert.

It'd be great to be able to upload both images and videos in one gallery. A nice feature would also be having these items clickable (either expand or redirected to a link). For example, I may want to upload short-form videos in a gallery and link them to their respective social media posts.

Ability to publish specific CMS items and standalone pages (instead of the whole site), as well as scheduling deploys for a later date.

Sorry, I might not explain this clearly... You can't create a component where each instance lets you select a different CMS item. The CMS collection isn't available as a variable that can be passed to component instances. If we could have that functionality it would help me make more of a newspaper style content platform where the lead image, title and category can be reused across the website... within a component to control the design...

Currently, when linking internally in Framer using a relative path (e.g. /blog?category=cms) within Dynamic Filters, the query parameters are ignored and only the base path (/blog) is applied. Query parameters only work when using the full absolute URL (e.g. https://domain.com/blog?category=cms ). This creates issues in staging environments or when changing domains, as absolute URLs break across different environments. It would be helpful if relative internal links preserved query parameters properly, so dynamic filters can work consistently across staging and production without requiring full absolute URLs.

The CMS Glossary is great for managing specific translations, but currently all entries must be added manually one by one. For teams with existing multilingual glossaries, this doesn’t scale. It would be very helpful to support bulk import of glossary terms via CSV (or similar), including translations across multiple languages. This would allow teams to migrate existing glossaries into Framer quickly, keep terminology consistent, and reduce manual setup time—especially for products supporting many locales.

It would be great if there was a maximum file upload size for CMS items. For example: if there is a Featured Image property it'd be great to set a max file upload size of 750kb.

I'd love for a slider, carousel or ticker component to be more dynamic with CMS content. At the moment they have to link to individual frames in order to create "slides", where I'd love for each slide to be an item in a Collection List from the CMS – this doesn't feel possible right now unless I'm missing something? This is so we could create dynamic carousels or slideshows from content in the CMS which can contain a variable amount of items in a collection list.

Nest CMS Blog Categories in a blog article URL /:category-slug/:blog-slug