Getting Started

Frame may be a very robust and intricate platform, but being an end user is easy! The Getting Started Guide will outline important details for end users such as minimum system requirements, supported browser versions, and a glossary of common Frame terms to help you get comfortable with the jargon. We’ll also show you how to access your Frame account.

Use the links in the drop-down menu below to jump to different sections of this guide, if needed.

Glossary of Frame Terms for End Users


Launchpad refers to the end-user-facing part of the Frame interface where users can go to launch and manipulate applications. End users can be given access to multiple Launchpads depending on the needs of their organization. For instance, one Launchpad may contain applications for word editing while another Launchpad houses only billing-specific apps. Administrators can configure multiple Launchpad interfaces to show what application sets specific end users see and what features are exposed to them. If enabled, end users can switch between Launchpads by clicking on the rectangular Launchpad list icon at the top of their screen. Launchpads are accessible via URL and may look something like this:

A Frame session refers to the connection between a user’s browser and an instance/virtual machine. A session is created the moment the connection is requested by the user and ends as soon as the connection is closed. Once a session is closed, the VM is prepared and made available for others to use.


This is a commonly used industry term for a virtual machine which includes a complete operating system as well as installed applications. Typically, multiple instances run simultaneously on a single physical server but are independent in every other way. An instance can come in a variety of types, with specifications that are like those for PCs and servers. For example, Frame instances are typically distinguished by the number of CPUs, amount of RAM, and the number of GPUs. The instance may also be referred to as the “VM” (virtual machine), the “system,” or the “workstation.” Frame supports many different instance types. Frame has named these instance types (e.g., “Air 4GB”, “Air 8GB”, “Pro 16GB”) to help differentiate them based on their specifications. Each Frame instance type name maps to an infrastructure provider-specific name.


Your administrator configures a pool of available instances for their group of end users based on the expected workload and activity. In an organization, for example, the billing department may start sessions from a pool of Air 4GB instance types while the graphic design department pulls from a pool of Pro 16GB instance types. The administrator can set the amount of available instances in the pool, including how many of those instances are buffered or “warmed up” and how many of each type are available to their end users at a given time.


Authenticating is how you prove your identity to access your Frame account. Your account administrator will decide how you authenticate to the platform. You may simply authenticate directly through the Frame platform with a user name and password or you may use a third-party SAML2 authentication method such as Okta.

Cloud Storage

Cloud storage refers to services such as Dropbox, Google Drive, Box, and Microsoft OneDrive which save your files on their public clouds as a service. Frame can connect to these cloud storage services to allow end users to save their work.

Disconnect and Close Sessions

When an end user exits a session, there are two options:

  • Disconnect from the session but keep it active, in which case the user can return to the session.

  • Close Session to completely end the session.

This distinction is important, so please read on:

  • “Disconnect” is like disconnecting your monitor cable from a running PC. In this case, if the system is set up with an “idle timeout” setting, the session will continue running and the user can connect back within the set time to resume their session.

  • “Close Session” is equal to what you do at the end of a day with a PC: you save all of your work and then power off the system. In Frame’s case, closing a production session will end the session completely. For most situations, your instance will be returned to the pool of production instances – making it available for someone else to use. For persistent desktop users, your persistent desktop can now be powered off safely.

System Requirements

Browser Requirements

The Frame Platform has been developed to deliver an application’s graphical user interface through any HTML5/WebGL compatible browser. While Frame may work on other HTML-capable browsers, Frame officially supports the latest two major versions of Chrome, Firefox, Safari, and Edge on the following operating systems.


Supported OS

Google Chrome

Windows, macOS, ChromeOS, Linux, iOS, Android

Mozilla Firefox

Windows, macOS, ChromeOS, Linux

Apple Safari

macOS, iOS

Microsoft Edge (Chromium)


For the best performance and most feature-rich experience, it is recommended to use Google Chrome whenever possible.


Frame does not support Internet Explorer and Opera browsers.

Mobile Browser Support

The Frame platform is officially supported on the mobile versions of Chrome, Microsoft Edge, and Safari. Desktop mode is not supported on mobile browsers at this time.

Frame App Requirements

Frame App is supported on the following operating systems.

Operating System

Supported Versions

Frame App for Windows

Windows 10 Home, Windows 10 Pro, Windows 10 Enterprise, Windows 10 IoT Enterprise

Frame App for Windows (Early Access)

Windows 11 Home, Windows 11 Pro, Windows 11 Enterprise, Windows 11 IoT Enterprise

Frame App for macOS

macOS Monterey (12.0+), macOS Big Sur (11.0+)

Frame App for Linux

Ubuntu 18.04, Ubuntu 20.04, and latest supported versions of IGEL OS, Stratodesk NoTouch OS, 10ZiG PEAKos, and ZeeTim ZeeOS

Device Requirements

The device used to access Frame will be dependent on your use case requirements. The table below describes the Optimal, Recommended, and Minimum hardware configurations for running a browser or Frame App.






Quad Core 3.0 GHz

Dual Core 2.4 GHz

Dual Core 1.5 GHz


8 GB

4 GB

2 GB

Discrete GPU





Use cases requiring multiple 4K monitors, high-fidelity multimedia, 3D rendering, video-conferencing, etc. will likely require the Optimal configuration or higher in order to achieve a suitable user experience.

Network Requirements

The following requirements must be met in order for the end user to access a Frame session:

  1. Support for HTTPS (TLS) connections on port 443 to the Frame Platform

  2. Support for HTTPS (TLS) and Secure WebSockets to the Frame-managed workload VM (FRP7)

  3. Support for UDP (DTLS) to the Frame-managed workload VM (FRP8)

Since the virtualized application window or desktop is streamed to the end user’s browser over the network, a user needs to have sufficient network bandwidth between their browser and the Frame-managed workload VM running the virtualized applications and/or desktop. The following table provides high-level guidance on average bandwidth consumption per Frame session based on the applications to be used, VM instance type (CPU only or GPU-backed), display resolution, and frame rate.

Average Bandwidth (Mbps)


VM instance type

Display resolution

Frame rate


Office productivity applications


up to 1920 x 1080

up to 20 fps


CAD applications


up to 1920 x 1080

up to 60 fps


Video editing/animation/sustained playback


up to 1920 x 1080

up to 60 fps


Video editing/animation/sustained playback


up to 3840 x 2160

up to 60 fps

In addition to the bandwidth requirements, the best user experience is with network latencies under 100 ms. Network latencies over 250 ms are not recommended. Also, jitter (change in latency) should be kept at a minimum as significant changes in both available bandwidth and latency can result a very poor user experience.

Frame App

Your account administrator may prefer you access your Frame account with Frame App. Frame app provides the same ease of use with Frame in a web browser, with additional functionality and benefits not yet available in Frame terminal. This section deescribes how to install, configure, and use Frame App as an end user.


The instructions below outline how to install Frame App on your endpoint as an end user.

  1. Start by navigating to your Launchpad in a compatible browser.

  2. From your Launchpad interface, click on your profile name in the upper right corner.

  3. You will see the option to download Frame App for the OS that you are accessing your account from. Other platform options will appear when you click on the arrow next to the provided OS.


Use the tabs below to find further installation instructions based on your endpoint device.


Frame App for Linux is only supported on Ubuntu and Ubuntu-based thin client OS that are Frame Ready validated (IGEL OS, Stratodesk NoTouch OS, Zeetim ZeeOS, and 10ZiG PeakOS).

  1. Click the download button, your download should automatically begin. Once downloaded, run the installer.

  2. Follow the prompts provided by the setup wizard, you will be asked to define the directory where you want the application installed.

  3. Click “Finish” after running through the installation wizard.

  1. Specify where you would like the file saved.

  1. Drag the file into the applications folder.

  1. Before starting Frame App, navigate to your System Preferences > Security & Privacy.

  2. Scroll down to Input Monitoring, unlock the dialog to make changes, and check the box next to Frame. Lock in your preferences.

  1. Launch Frame App when you’re ready to begin using it.

  1. On your Linux endpoint, open a terminal window and navigate to the location where you have downloaded Frame App. Take note of the version number of Frame App.

  2. Run sudo apt install plus the file name/location, as shown below:

  1. Once installed, you should be able to access Frame App from your App Launcher.

Using Frame App

While Frame was designed to be accessed from an HTML5-enabled browser, some end users may access their Frame environment from Frame App. Frame App provides additional features to organizations that aren’t available through a modern web browser. If you are accessing your account from Frame App, we will cover some of the basics here. If you are accessing your account from your web browser, you can move on to the next section.

To launch Frame App from your local machine, simply click on the icon:


Using Frame App is simple, and there are only a few differences from using Frame in a web browser.


The menu options and definitions are as follows:

  • Frame > Quit Frame: Closes the window. If you select this option while in a session, your session will only disconnect. You will still be able to access your session by relaunching Frame App. More details are covered in the next guide.

  • View > Reload: Reloads the window. Performs the same action as the “refresh” button in a web browser.

  • View > Show Certificate: This window displays SSL information that you may be asked to access for troubleshooting reasons.

  • View > Toggle Full Screen: Enables/disables full screen mode.

  • History> Back/Forward: The Frame App equivalent of the back and forward buttons in a modern web browser.

  • Help > About: Provides information about Frame App including your current version and a link to our EULA.

  • Help > Preferences: Opens the “preferences” window where your administrator will set the startup URL for Frame App.

Frame App User Preferences

This section will help direct you on how to modify your Frame App preferences from within the app. This is only available with Windows and macOS Frame App. To access the “Preferences” page, select it from the “Help” menu in Frame App.

Startup URL

Administrators can modify the startup URL for Frame App from this page. By default, the startup URL is set to


Startup URL Destination

The startup URL can be modified to point to a specific destination. For example, if you had a particular Launchpad in mind, it may look like the following:


As shown in the graphic above, the URL defines the customer entity, organization entity, account name, and lastly, the Launchpad name. The user will be prompted to log in with their credentials before being directed to the specified Launchpad.

Startup URL Authentication

Many organizations choose to integrate Frame with a third-party SAML2 auth provider. In this case, there is a very simple way administrators can ensure their users validate through the desired auth provider before moving on to their startup destination.

  1. Under the “Startup URL” field, define the URL where the SAML2 auth provider has been configured. In this example, our SAML2 integration is at the organization level, so we will start there:

  1. Next, append ?idp= to the URL, followed by auth provider integration name. In this example, the URL is pointing to our Azure AD integration (tutorial-azureAD). Click “Save” to apply your changes.

  1. To test, close Frame App and re-launch it. You will automatically be prompted to log in with your SAML2 provider credentials before going to the startup destination.


Now that we have specified our Azure AD integration as the IdP, we’re automatically prompted for our Microsoft credentials.

Accessing your Account

It’s finally time to sign in to your Frame account. Depending on how your administrator has configured your account, there are two methods you can use to set up and access your account.

Authenticated Sign In

Many organizations choose to leverage a third-party identity provider (IdP) to control their users’ access to various tools and platforms. There is no need to set up your account credentials since your organization can simply provide Frame access to you through the third-party IdP. Frame integrates with most SAML2 identity providers, which means you may access your Frame account in a variety of ways. Accessing Frame through your IdP is simple, we will outline the different methods below.

Sign In

If your administrator has configured the Frame account to authenticate users through your organization’s SAML2 provider, they will typically provide you with a login URL which should look something like this:

If you are not already authenticated with your IdP, your sign on screen may look something like this:


Notice the “Sign in with Okta” button with the yellow lock symbol

In this example, Okta is the identity provider. Your administrator may use another provider such as Microsoft Azure AD, Microsoft ADFS, Google Suite, or others. Click on the “Sign in with ____” button to authenticate to the platform. You will be redirected to your identity provider’s login page where you’ll be prompted to enter your IdP credentials. Once you log in, you will automatically be taken to the Frame platform.

URL Authentication

Your administrator may have optimized your Frame login URL to authenticate through your IdP. If so, the URL they provide you may look something like this:

Launch Frame from IdP

Identity providers often supply end users with a landing page where they can select from their available applications and launch them, pre-authenticated. As an end user, you may see Frame as an option. Using Okta as an example, you may be able to select your Frame “chiclet” from the Okta “My Apps” page:


In this case, starting Frame is as simple as clicking on the button. Many IdPs provide a similar interface to their end users.

Basic Sign In

If your admin has opted to use the built-in Frame platform sign in feature, you will set your own credentials to access your account. The first thing you will need to do is check your email to see if you have received your invitation.


You’ve been invited!

Open the email and click the blue button to proceed.


Fill in your user details and click “Set Password.”


Once you’ve set your user name and password, click “Proceed to Login.” You’ll be asked to log in with your new credentials.

From this point forward, you can log in to your Frame platform account by going to and clicking “Sign in with email/password.”


Forgot your Password?

If you find that you have forgotten your password, simply click on the “Forgot your password?” link below the sign in button and follow the prompts. You will receive an email with reset instructions. If you authenticate using a third-party SAML2 or OAuth2 provider, please contact your administrator to reset your password.

All set! You can move on to the next End User guide if you’re ready!