A custom React component written in code that extends Framer's capabilities beyond built-in features. Code components enable advanced functionality like custom animations, API integrations, and complex interactive elements. They live alongside visual components and can accept properties that designers control without touching code.

A JavaScript function that modifies component behavior without changing the component itself, enabling custom interactions and logic. Overrides let you add functionality like form validation, state management, or API calls while keeping components reusable. This separation of concerns keeps your component library clean while allowing page-specific customizations.

Framer's backend functionality enabling server-side operations, data processing, and secure integrations. Server APIs handle operations that shouldn't or can't run in the browser, like secure API calls. Use server APIs for authentication, database operations, and sensitive processing.

Software application used to access and display websites, including Chrome, Safari, Firefox, and Edge, each with slightly different rendering behaviors. Cross-browser compatibility ensures your site works correctly for all visitors regardless of their browser choice. Framer generates clean, standards-compliant code that renders consistently across modern browsers.

Internet Protocol address—a numerical label identifying devices on a network, like 192.168.1.1 or a longer IPv6 format. IP addresses enable communication between devices and can provide geographic location data for analytics. CDNs route traffic based on IP to serve content from nearby servers.

JavaScript Object Notation—a lightweight data format for storing and transmitting structured data, widely used in web APIs. JSON's human-readable syntax makes it easy to work with for configurations and data exchange. Framer uses JSON for various configurations and API integrations.

A browser API for making network requests from JavaScript using promises. Fetch is commonly used to retrieve external data and populate dynamic UI or CMS workflows.

Partner Models are external foundation models exposed through a single product interface. Product teams often combine them with Model Routing and governance artifacts like a Model Card.