Limitations and library changes

This topic describes limitations and feature behavior changes when a Streamlit feature works differently in Snowflake than in the open-source library.

Unsupported Streamlit features

The following Streamlit features are not supported in Streamlit in Snowflake:

Limitations when loading external resources in Streamlit in Snowflake

All Streamlit in Snowflake apps run within the Content Security Policy (CSP) that restricts which resources can be loaded. Snowflake blocks loading code — including scripts, styles, fonts, and iframe embedding — from any external domain. However, loading a subset of resources from Mapbox is supported.

When you use the st.map or st.pydeck_chart Streamlit commands, Mapbox provides the map tiles when rendering map content. Mapbox is a third-party application and is subject to Snowflake’s External Offerings Terms.

Loading images or media from external domains is supported in Streamlit in Snowflake, but not in the Snowflake Native App Framework.

For example, the following code runs without a Python error, but the script is not loaded or executed in the browser:

# This will not work
import streamlit.components.v1 as components
components.html("""
<script src="http://www.example.com/example.js"></script>
""", height=0)
Copy

The CSP also blocks front-end calls that are generally considered unsafe, such as eval().

Note

App developers are responsible for security checks and the software supply chain of Streamlit in Snowflake app code per the Snowflake’s Shared Responsibility Model.

Additional Streamlit in Snowflake limitations

Streamlit in Snowflake has the following additional limitations:

Streamlit apps have a limit for retrieving data

Streamlit apps running in Streamlit in Snowflake and in a Snowflake Native App have a 32-MB limit on the size of messages exchanged between the backend and the frontend. Queries that exceed 32 MB return the following error:

MessageSizeError: Data Size exceeds message limit

To avoid this limit, design your Streamlit apps to retrieve data in increments smaller than 32 MB.

Streamlit in Snowflake only supports internal stages that use client-side encryption

The Streamlit in Snowflake editor does not support creating a STREAMLIT object from files on a named stage that uses server-side encryption. In this situation, Snowsight returns an error.

st.cache_data and st.cache_resource are not fully supported

st.cache_data and st.cache_resource are not fully supported in Streamlit in Snowflake. Caching only works within a single session. Cached values can’t be carried over to other sessions and shared between different users of a Streamlit app.

st.file_uploader has a limit of 200 MB for uploaded files

When using st.file_uploader, you may upload files limited to 200 MB each. Configuring this is currently not supported in Streamlit in Snowflake. For larger files, consider processing data in smaller batches or using alternative uploading methods.

Changes when working with query parameters in Streamlit in Snowflake

For st.query_params in Streamlit in Snowflake, a streamlit- prefix is added to each query parameter key in the URL. This prefix is not included when using st.query_params to get or set a value.

For example, consider the following URL:

https://app.snowflake.com/org/account_name/#/streamlit-apps/DB.SCHEMA.APP_NAME?streamlit-first_key=one&streamlit-second_key=two

The parameters in this URL are accessible in st.query_params as the following key-value pairs:

{
   "first_key" : "one",
   "second_key" : "two"
}
Copy

For more information, see st.query_params.

Language: English