> 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/prepare-a-figma-file-for-a-dscout-study.md).

# Prepare a Figma file for a Dscout study

*This article outlines recommendations and best practices for preparing Figma files for **unmoderated studies**. While you may find some of this guidance helpful for testing Figma files in interview studies, some of the settings and recommendations outlined here will not apply.*

{% hint style="info" %}
**Note:** The guidance in this article applies to traditional Figma prototypes. It does not apply to prototypes created with Figma Make. To test a **Figma Make** **prototype** in Dscout, first [publish](https://help.figma.com/hc/en-us/articles/31304586129559-Publish-update-or-unpublish-a-functional-prototype-or-web-app) the prototype in Figma Make. Then, add the provided link to your task question using the **URL** option.
{% endhint %}

When you link a Figma prototype in a Dscout study, all frames and pages within that file have to be loaded and processed. This might cause importing issues, or make your prototype slow to load and respond for your testers.

We highly recommend following these steps to create a dedicated and optimized testing file:

## Create a dedicated testing file

We highly recommend [duplicating](https://help.figma.com/hc/en-us/articles/360038511533) your prototype into a dedicated testing file to ensure successful loading and processing. Before adding your prototype link, exclude pages and frames that are not relevant to your test and avoid using sections unless needed for prototyping. This will create a lightweight file to improve load times and reduce errors.

{% hint style="info" %}
**Note:** 100 MB is the maximum supported file size.
{% endhint %}

You will also want to add a note to your duplicated test file stating that it is linked to a Dscout study to prevent changes from being made to the file.

## Naming your frames, layers, and components

Give your frames, layers, and components easy-to-identify names to get the most out of your prototype test. Analyzing click maps and click events is much easier with well-named layers.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/1kkAkyeSm3SLaTyh45UL/32524108306452)

## Set a prototype flow starting point (required)

Your prototype must have a flow starting point before you can add it to Dscout. By default, participants start on this frame. You can also choose a different starting screen for each task question in Dscout. For more information, see [Starting screen](https://help.dscout.com/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study.md#starting-screen).

For how to add a flow starting point in Figma, see Figma's help article on [prototype flows](https://help.figma.com/hc/en-us/articles/360039823894-Create-and-manage-prototype-flows).

## Optimize your prototype

Avoid importing issues and slow loading for participants by optimizing your prototype design.

* Compress your images before uploading them to Figma. Images are not compressed automatically by Figma, and uncompressed images can lead to large file sizes.
* Convert vectors to JPG images
* Use Smart Animate sparingly
* Remove all pages from your file except for the page that contains the prototype you are using in your study
* Limit the size and number of frames to only include the frames that are necessary for the study

## Avoid overlapping layers and scroll frames

To capture click data for the entire screen, avoid overlapping layers and placing *scrolling* frames on top of other frames. Double-check that any scrolling frames are cropped to match the width of their content and do not overlap other components, frames, or layers on your screen. See the example below.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/t8NQYrb8IBDT27vXMUqV/32524108313364)

## Recommended prototype options

After you add your prototype to a task question, you can control how participants view it from the **Prototype settings** in Dscout. We recommend:

* **Scaling:** For desktop prototypes, use **Fit width**. For mobile prototypes, use **Fit width and height**.
* **Hide Figma UI:** Keep this on so participants can't jump to other flow starting points or page through your screens with Figma's navigation arrows. Dscout turns this on by default unless your prototype link already turns it off.
* Depending on your prototype and study design, you may also want to change **Hide Figma hints on click** and **Enable Figma shortcuts**.

![](https://content.gitbook.com/content/IKfn7RcT4CW9XaIbqAdd/blobs/RWxGMwlH1OmtEnjSxiiB/32524108317716)

Display settings saved in your Figma prototype link carry over to Dscout, and you can review or change them at any time in Dscout. For more information, see [Scaling](https://help.dscout.com/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study.md#scaling) and [Advanced settings](https://help.dscout.com/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study.md#advanced-settings).

## Mobile prototype tip - preview your mobile prototype

Always check your mobile prototype on your mobile device ***before*** launching your study by opening your prototype link in your phone's browser.

Your mobile prototype will load for participants inside of a regular mobile browser window, so the browser's header and footer will still be visible. Checking the prototype on your device will help ensure that it’s behaving correctly with the browser UI present.

## Share link settings and permissions (required)

Before directing participants to a Figma prototype, make sure they can access it. We recommend sharing your prototype so that anyone with the link can view it. However, Dscout does support password-protected Figma files in both mobile and desktop studies.

{% hint style="success" %}
**Tip:** When testing a password protected Figma file, be sure to include the password in the prompt of the related question in your study so users can access it when needed.
{% endhint %}

If you are inviting your own participants, double-check your share settings to ensure those you invite can access your prototype. If you plan to share privately, make sure your participants have all been invited to view it.

For how to change share settings in Figma, see Figma's help article on [sharing files and prototypes](https://help.figma.com/hc/en-us/articles/360040531773-Share-files-and-prototypes).

## Sharing your Figma prototype (required)

Once your Figma file is ready, copy your prototype's link from Figma and add it to a task question in Dscout. **Be sure to copy the prototype link, rather than the design file link.**

Before you copy the link, confirm your share settings and prototype options described above. For how to copy a prototype link in Figma, see Figma's help article on [sharing files and prototypes](https://help.figma.com/hc/en-us/articles/360040531773-Share-files-and-prototypes).

Next, add the link to your study. For more information, see [Add a Figma prototype to a study](https://help.dscout.com/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
