Plugin best practices

Learn how to create high-quality plugins that users can trust and enjoy using.

Great plugins solve real problems, provide a polished experience, and continue delivering value over time. While these recommendations are not requirements, they can help improve quality, discoverability, and trust in the Framer Community. Use this checklist as a reference while building, publishing, and maintaining your plugin.

General

A strong plugin solves a clear problem, delivers on its promise, and provides a reliable experience.

  • The plugin solves a clear user need.

  • The plugin delivers the functionality described in its listing.

  • Setup, usage, and troubleshooting documentation are available.

  • External dependencies are limited to those that are necessary.

  • Authentication-based plugins provide a logout option through a header menu.

  • The plugin is actively maintained as Framer evolves.

Performance

Fast and reliable plugins create a better experience for users.

  • The plugin loads quickly.

  • Network requests are minimized.

  • Common workflows and edge cases have been tested.

  • Loading, empty, and error states are handled gracefully.

  • CPU and memory usage remain reasonable.

  • The plugin remains responsive during common tasks.

Usability and design

Simple, intuitive experiences are easier to learn and use.

  • The interface is clean and easy to understand.

  • Light and dark mode are supported.

  • Labels, controls, and interactions are consistent.

  • Assets and icons are high quality.

  • The plugin UI is written in English.

  • The experience aligns with Framer’s design language where appropriate.

Safety and security

Users should understand how your plugin works and feel confident using it.

  • The plugin only requests permissions that are necessary.

  • Authentication flows are clear and reversible.

  • External services are secure and transparent.

  • User privacy and applicable regulations are respected.

  • User data is handled responsibly.

  • The codebase is clean, maintainable, and secure.

Creators are responsible for ensuring their plugins comply with applicable laws and licensing requirements.

  • All assets, code, and content are properly licensed or owned by the creator.

  • Relevant open-source licenses are followed.

  • Attribution is provided where required.

  • Pricing, account requirements, and external services are clearly communicated.

Marketplace

Your marketplace listing should accurately represent your plugin and set clear expectations.

  • The listing accurately represents the plugin.

  • Authentication requirements are clearly disclosed.

  • Primary use cases and unique features are clearly explained.

  • Pricing details are accurate and up to date.

  • Paid plugins display pricing in USD ($).

  • Marketing claims are accurate and not misleading.

Thumbnails

A strong thumbnail helps users quickly understand what your plugin does.

  • The thumbnail clearly shows the plugin or its interface.

  • The visual is simple, focused, and easy to understand.

  • Unnecessary text and decorative elements are avoided.

  • Assets are sharp and high quality.

  • The thumbnail accurately represents the plugin experience.

Support

Supporting your plugin helps build trust with users over time.

  • Available support options are clearly explained.

  • Documentation is complete and up to date.

  • Setup requirements and limitations are documented.

  • Users know where to get help if they encounter issues.

  • The plugin is maintained and updated as Framer evolves.

Great plugins solve real problems, provide a polished experience, and continue delivering value over time. While these recommendations are not requirements, they can help improve quality, discoverability, and trust in the Framer Community. Use this checklist as a reference while building, publishing, and maintaining your plugin.

General

A strong plugin solves a clear problem, delivers on its promise, and provides a reliable experience.

  • The plugin solves a clear user need.

  • The plugin delivers the functionality described in its listing.

  • Setup, usage, and troubleshooting documentation are available.

  • External dependencies are limited to those that are necessary.

  • Authentication-based plugins provide a logout option through a header menu.

  • The plugin is actively maintained as Framer evolves.

Performance

Fast and reliable plugins create a better experience for users.

  • The plugin loads quickly.

  • Network requests are minimized.

  • Common workflows and edge cases have been tested.

  • Loading, empty, and error states are handled gracefully.

  • CPU and memory usage remain reasonable.

  • The plugin remains responsive during common tasks.

Usability and design

Simple, intuitive experiences are easier to learn and use.

  • The interface is clean and easy to understand.

  • Light and dark mode are supported.

  • Labels, controls, and interactions are consistent.

  • Assets and icons are high quality.

  • The plugin UI is written in English.

  • The experience aligns with Framer’s design language where appropriate.

Safety and security

Users should understand how your plugin works and feel confident using it.

  • The plugin only requests permissions that are necessary.

  • Authentication flows are clear and reversible.

  • External services are secure and transparent.

  • User privacy and applicable regulations are respected.

  • User data is handled responsibly.

  • The codebase is clean, maintainable, and secure.

Creators are responsible for ensuring their plugins comply with applicable laws and licensing requirements.

  • All assets, code, and content are properly licensed or owned by the creator.

  • Relevant open-source licenses are followed.

  • Attribution is provided where required.

  • Pricing, account requirements, and external services are clearly communicated.

Marketplace

Your marketplace listing should accurately represent your plugin and set clear expectations.

  • The listing accurately represents the plugin.

  • Authentication requirements are clearly disclosed.

  • Primary use cases and unique features are clearly explained.

  • Pricing details are accurate and up to date.

  • Paid plugins display pricing in USD ($).

  • Marketing claims are accurate and not misleading.

Thumbnails

A strong thumbnail helps users quickly understand what your plugin does.

  • The thumbnail clearly shows the plugin or its interface.

  • The visual is simple, focused, and easy to understand.

  • Unnecessary text and decorative elements are avoided.

  • Assets are sharp and high quality.

  • The thumbnail accurately represents the plugin experience.

Support

Supporting your plugin helps build trust with users over time.

  • Available support options are clearly explained.

  • Documentation is complete and up to date.

  • Setup requirements and limitations are documented.

  • Users know where to get help if they encounter issues.

  • The plugin is maintained and updated as Framer evolves.

FAQ

  • Are these best practices required?

    No. These recommendations are intended to help creators build higher-quality plugins and provide a better experience for users. You can apply the guidance that makes sense for your plugin and workflow.

  • What should I do before publishing my plugin?

    Review the checklist above and address any items relevant to your plugin. Clear functionality, strong performance, accurate documentation, and transparent communication can help create a better experience for users.

  • Why should I follow these recommendations?

    Plugins that are polished, reliable, and well documented are easier for users to trust. Following these best practices can improve discoverability, reduce support requests, and help your plugin reach more users.

Updated