A panel is a defined section in the user interface dedicated to specific functionalities or content management. Panels enable users to customize elements and widgets directly on-stage.
Accessed through the component's GFPP (Graphic Floating Properties Panels), panels are presented as draggable floating layers over the editor, typically positioned beside the component. Panels are designed to expose the stage and provide immediate feedback on changes users make in the panel.

Every panel has three main sections:
1. Header
2. Content Area
3. Footer

The panel header describes the purpose of the panel and provides users with a context about what they're interacting with. Additionally, it can include actions to key functions, such as closing the modal or help navigation.

1. Title (mandatory)
The title follows the format of stating the name of your widget or element first, followed by the name of the action. For example, if your element is "Menu" and the action is "Settings," the panel should be named "Menu Settings."
The title shouldn't include call-to-action.
Title is mandatory.
2. Back button
The back button allows users to go back to the previous state and is used in drill-in mode only.
3. Help button
The help button opens a link to the help center panel which contains a short article relevant to the widget or element, and a search bar for more help.
4. Close button (mandatory)
The close button allows users to exit the panel. Users can also exit the panel using ESC, or by clicking outside of the panel on any other element.
Close button is mandatory.
The content area is the space to display controls, input fields, customisation options, media, and any other information related to the chosen element or widget.
Sticky footer is optional and can be used for actions that you want to remain visible at all times, such as a list of items.


A divider is a thin line that groups content in the panel. Dividers are displayed by default in Classic, but not in Studio. You can enforce show/hide by using the divider prop or adding a divider manually.

Dividers enabled automatically after every control

By default dividers are disabled
Don't display disabled controls as they can frustrate users who may attempt to edit them. Instead, hide these controls until the relevant feature is triggered by the user.

Hide controls that can't be edited

Disable content that can't be edited
There are 10 types of panels that can be created for your app:
Settings panel is used to control the content of the element or an app or where they can start up the app and define its general functionality.

What should go inside the Settings panel?
Manage panel is responsible for editing components with multiple items (for example, tabs, radio buttons, dropdown, menus etc.).
The Manage items panel should have a fixed height: 576px ( which is the panel max height), it's also common to use the footer with one or two CTAs like "Add Items".

What should go inside the Manage panel?
Layout settings are responsible for changing the composition, spacing between elements, overflow and other resize behaviors of the element that can't be controlled from stage.

What should go inside the Layout panel?
Design panel is an Editor platform API, it is used for all the design properties of the stage element.

What should go inside the Layout panel?
The behaviors panel contains hover and click interactions to the component.

What should go inside the Layout panel?
Data panel is used to connect elements to data by adding a dataset and linking values to a database.

What should go inside the Connect to Data panel?
The Animations panel lets you customize an animation and apply it to a selected element. Every element gets this panel when it is created, so you only decide whether animations suit your element or app.

Link panel is an Editor platform API, it can be used through GFPP or from controls that require a link. The API can be modified to use only specific link options or all link options, depending on your product requirements.

Stretch content is a platform panel which is used to make relevant components stretch to screen size. This panel exists only in Classic editor since Studio has a different responsive mechanism.

Some components/apps require a unique setting panel that's doesn't fit the default types, for example: filters, masks, interactions, shape dividers.

When we write, we're designing consistent experiences. Many similar experiences are designed across Wix products which is why it can be helpful to refer back to this guide to follow best practices.
Note: For consultation, contact the UX writers. The decision is theirs.
The panel title is the heading of the entire panel. Panel titles are used to explain what the panel is about.

A field label is the label (or title) of an input field. Field labels are used to explain what type of information users need to add to an input field.

Write labels as guiding questions according to the situation.

Write generic description to the control function.
Sections are used to divide between different property groups of the element.


Back buttons should say only "Back". For example, in a design tab the back button should say "Back" and not "Back to Design" since we are already in the Design Tab.

Use only "Back".

Don't use "Back to Page Name".
For example, in the text section, there's no need to mention text in every label.

Be clear and concise.

Don't repeat the name of the tab in field labels.
Avoid using brackets parentheses unless absolutely necessary.

Use input suffix to show unit value.

Don't Use brackets or parentheses unless absolutely necessary.
Keep in mind that text tends to be longer when translated into other languages, and panels have a fixed width.

Last updated: 21 October 2026