> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study.md).
# Add a Figma prototype to a study
| Study type | Availability |
|---|
| Usability tests | true |
| Intercept studies | true |
When conducting studies, it can be useful to have participants interact directly with a website or prototype to get a sense for what they like or dislike, what design elements are working, or what could be improved.
To make sharing prototypes easier, you can embed links to prototypes directly in task questions. Then, when participants reach these points in your study, the prototype will open automatically.
{% hint style="info" %}
Before adding your Figma prototype, it’s important to optimize it for use by participants. For more information, see [Preparing your Figma file for testing](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study.md).
{% endhint %}
## Add a prototype to a study
You can add a Figma prototype to a study at the study level or through individual task questions. Either way, once you’ve added a prototype once, you can use it in multiple questions throughout your study.
{% hint style="warning" %}
Prototype files must be 100 MB or smaller to be used in studies.
{% endhint %}
**To add a prototype at the study level:**
{% stepper %}
{% step %}
On the **Usability test/Mission** tab of your study, click the **Task URLs** button in the top right corner.
{% endstep %}
{% step %}
Click **+ Add task URL**.
{% endstep %}
{% step %}
Select **Figma prototype**.
If you haven’t already, you’ll be prompted to connect Dscout to your Figma account. For more information, see [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration.md).
{% hint style="info" %}
If you're using a Figma Make prototype, first [publish](https://help.figma.com/hc/en-us/articles/31304586129559-Publish-update-or-unpublish-a-functional-prototype-or-web-app) your prototype in Figma Make. Then, add the provided URL as a **Website**. Heat maps are not generated for Figma Make prototypes.
{% endhint %}
{% endstep %}
{% step %}
Enter the **URL** for your prototype. This should be the share link for your prototype, not the link to your overall Figma design file.
{% hint style="info" %}
We recommend setting your Figma share settings to **Anyone with the link** to ensure participants can access your prototype. For more helpful tips, see [Preparing your Figma file for testing](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study.md).
{% endhint %}
{% endstep %}
{% step %}
Click **Add**. Depending on the size of your prototype, the connection may take a minute or two. When the prototype is connected, you’ll see the name of your prototype and a chip indicating it is **Connected**.
{% endstep %}
{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}
Now, the prototype is added to your study and you can use it when adding new task questions. Simply click **Add** beside **Task URL**, then select from the list of **Previously added** prototypes. For more information, see [Task questions](/study-basics/question-types/task-questions.md).
**To add a prototype using a task question:**
{% stepper %}
{% step %}
On the **Usability test/Mission** tab of your study, click **Add** in the center of the builder or in the left sidebar.
{% endstep %}
{% step %}
Under **Usability**, select **Task**.
{% endstep %}
{% step %}
Enter the **Task** prompt or instructions.
{% endstep %}
{% step %}
Click **Add** beside **Task URL**.
{% endstep %}
{% step %}
Select **Figma prototype**. (Or, select from the list of **Previously added** prototypes to use one that’s already in your study.) If you haven’t already, you’ll be prompted to connect Dscout to your Figma account. For more information, see [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration.md).
{% hint style="info" %}
If you're using a Figma Make prototype, first [publish](https://help.figma.com/hc/en-us/articles/31304586129559-Publish-update-or-unpublish-a-functional-prototype-or-web-app) your prototype in Figma Make. Then, add the provided URL as a **Website**. Heat maps are not generated for Figma Make prototypes.
{% endhint %}
{% endstep %}
{% step %}
Enter the **URL** for your prototype. This should be the share link for your prototype, not the link to your overall Figma design file.
{% hint style="info" %}
We recommend setting your Figma share settings to **Anyone with the link** to ensure participants can access your prototype. For more helpful tips, see [Preparing your Figma file for testing](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study.md).
{% endhint %}
{% endstep %}
{% step %}
Click **Add**. Depending on the size of your prototype, the connection may take a minute or two. When the prototype is connected, you’ll see the prototype's name and connection status.
{% endstep %}
{% step %}
Configure any other required settings for your task question. For more information, see [Task questions](/study-basics/question-types/task-questions.md).
{% endstep %}
{% step %}
Click **Done**.
{% endstep %}
{% endstepper %}
Now, you’ve successfully added a prototype using a task question. The URL for this prototype will also be accessible in your entire study so you can add it to subsequent questions if needed.
Once you’ve added your prototype, you can also select a screen where you want participants to start as well as a screen that indicates successful completion of the requested task in your prototype.
## Prototype settings
### Starting screen
By default, prototypes will open on the starting frame set within your Figma file. However, you can customize the starting screen for each individual task question in your study. So, if you use one prototype for multiple tasks, you can have each of them start on a specific screen instead of all the way at the beginning of your prototype.
{% stepper %}
{% step %}
Navigate to the task question where you want to set a starting screen.
{% endstep %}
{% step %}
Under **Task flow**, hover over the image beneath **Starting screen** and click **Edit**. The **Select starting screen** modal is displayed.
{% endstep %}
{% step %}
Use your keyboard’s arrow keys to navigate through your prototype to find the screen you want. If you want to go back to the beginning at any point, click the **R** key.
{% endstep %}
{% step %}
Once you’ve found the screen where you want this task question to start, click **Save as starting screen**. Your selected screen will now display beneath **Starting screen** when editing your question.
{% endstep %}
{% step %}
Click **Done** to save the task.
{% endstep %}
{% endstepper %}
Now, when participants reach this task question, the prototype will open on your designated starting screen rather than the default starting frame of your Figma file. This helps ensure participants all begin each task on the same page—literally.
### Success screen
In addition to setting a starting screen, you can also select a specific screen of your prototype that, when reached by a participant, indicates they were able to successfully complete what you asked them to do. You’ll be able to see which participants reached this success screen during analysis.
{% stepper %}
{% step %}
Navigate to the task question where you want to set a success screen.
{% endstep %}
{% step %}
Under **Task flow**, click **Add** beneath **Success screen**. The **Select success screen** modal is displayed.
{% endstep %}
{% step %}
Use your keyboard’s arrow keys to navigate through your prototype to find the screen you want. If you want to go back to the beginning at any point, click the **R** key.
{% endstep %}
{% step %}
Once you’ve found the desired screen, click **Save as success screen**.
Your selected screen will now display beneath **Success screen** when editing your question.
{% endstep %}
{% step %}
Click **Done** to save the task.
{% endstep %}
{% endstepper %}
Now, when participants reach the success screen during the task, this data will be included in their response and you’ll be able to see it during analysis.
### Scaling
Depending on what you're designs are emulating (an app or a website, for example), the size of your prototype may vary. With scaling options, you can determine how your prototype is displayed to participants. To access these settings, click the **Prototype settings (gear)** icon on your prototype. Then, select whether your prototype has a device frame or not:
{% hint style="info" %}
For more information on scaling options, see Figma's [Play your prototype](https://help.figma.com/hc/en-us/articles/360040318013-Play-your-prototypes#h_01HER6XXFTAK565E14WGYEM4T4) article.
{% endhint %}
Selecting **Without a device frame** displays the following **Scaling** options:
| Setting | Description |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Actual size (100%)** | Displays the prototype based on the full size of the design frame. Depending on the frame and the screen size, this may result in a cropped prototype. |
| **Fit width and height** | Shrinks the prototype so that both the width and the height fit within the viewer window. It will not scale up the prototype. |
| **Responsive** | Resizes and re-layouts the prototype with the participant based on applied constraints and auto layout settings. This lets you test designs at different window sizes for responsiveness. For Responsive behavior, constraints and auto layout must be applied in Figma. |
| **Fit width** | Scales the prototype so it fills the width of the display. |
| **Fit screen** | Scales the prototype horizontally and vertically so that it fills the entire display. It will not overflow any content of the design. |
Selecting **With a device frame** displays the following **Scaling** options:
| Setting | Description |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Responsive** | Resizes and re-layouts the prototype with the participant based on applied constraints and auto layout settings. This lets you test designs at different window sizes for responsiveness. For Responsive behavior, constraints and auto layout must be applied in Figma. |
| **Fit device on screen** | Shrinks the device frame so that it fits within the participant's window. |
| **Zoom device to fill screen** | Scales the device so that it fills the entire display. |
### Advanced settings
Dscout offers additional prototype settings to control how your participants can interact with your designs. To access these settings, click the **Prototype settings (gear)** icon. Then, select whether your prototype has a device frame or not:
The following options are displayed:
| Setting | Description |
| ----------------------------- | ---------------------------------------------------------------------------------------- |
| **Hide Figma UI** | Turns off all Figma interface elements such as the bottom toolbar and navigation arrows. |
| **Hide Figma hints on click** | Hides visual cues that indicate which areas of your prototype are interactive. |
| **Enable Figma shortcuts** | Allow users to navigate your prototype using keyboard shortcuts. |
## Re-sync a prototype
To generate [heat maps](/study-basics/testing-prototypes/analyze-heat-maps-and-click-data.md), Dscout relies on the most recently synced version of your prototype. So, if you make updates in Figma you want reflected in the heat maps generated by Dscout, you’ll need to re-sync your prototype. **Re-syncing a prototype does not impact the participant experience in any way as they will always be directed to the most up-to-date version of the prototype linked in the study.**
{% hint style="info" %}
Prototypes are only synced if you have the Figma integration enabled. For more information, see [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration.md).
{% endhint %}
### To re-sync a prototype
{% hint style="warning" %}
Only re-sync a prototype if critical changes have been made *and* if no participants have completed the study using the old version of your prototype. Doing so can cause inconsistencies in your data during analysis.
{% endhint %}
{% stepper %}
{% step %}
On the **Usability test/Mission** tab of your study, click **Task URLs**.
{% endstep %}
{% step %}
Click the re-sync button beside the prototype. A confirmation modal is displayed.
{% endstep %}
{% step %}
Click **Re-sync Figma prototype** to confirm.
{% endstep %}
{% endstepper %}
Now, Dscout processes your prototype again, re-syncing with the latest version for use when generating heat maps and click event data.
{% hint style="info" %}
If you encounter any issues when adding a Figma prototype to a task question, check out our [Figma Troubleshooting Guide](/integrations/figma-integration/troubleshooting-a-figma-prototype.md) for help.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.dscout.com/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.