Shared view URL filters

Understanding and using shared view URL filters

After creating a share for your view you can add filtering conditions in the URL that will determine which to records will be revealed when the view is loaded on a browser.

For example, the URL https://airtable.com/shrsa57bWpEecPtzp?filter_Category=Industrial%20design will take you to a shared view where a condition is showing just the records where the “Category” field is “Brand identity”.

Common considerations:

• Users can easily remove this condition in the "Filters" menu, so you shouldn’t use this feature to hide private data.

• This feature does not limit what data is loaded, instead, it loads the entire original shared view, and then applies additional filtering conditions to it.

• In those cases, you might create a view in Airtable for each person and generate a share view link matching each person or consider using Interface Designer to share data with more granular permissions set.

Inputting a URL filter

To add filtering conditions you need to add to the query string of a URL. Query strings are a developer feature of websites, but in this article we’ll explain how to use them. You can also use Airtable formulas to help construct a query string.

To build a filtering condition, first, think about what you want to express in words. We’ll be building a share URL filter for this share: https://airtable.com/shrsa57bWpEecPtzp, one that represents that “The Category field equals Brand identity and the Project lead field contains Cameron Toth”. Our filter has two rules:

• Category equals Brand identity

• Project lead contains Cameron Toth

Filtering condition rules are written in the format filterxxxx_{Field}={Value} where you replace {Field} and {Value} with your own field and value and the “xxxx” portion refers to the different filter operators cover in the “Supported URL filter operators” section below.

Query strings don’t support many characters like spaces or commas so you need to URL encode fields and values when they contain those special characters. You may also use the Airtable ENCODE_URL_COMPONENT() function in a formula field. So, for our category value to be used in the URL we would want to encode it as Brand%20identity, where %20 is a space.

Note

A field ID can be used instead of the field name. Field IDs are available through Airtable’s API, or through the Field Manager (paid plans only). Using Field IDs vs. Field Names:

• Format with field name: ?filter_Category=Brand%20identity

• Format with field ID: ?filter_fldXXXXXXXXXXXX=Brand%20identity

Benefits of using field IDs:

• More stable (field names can change)

• Works even if fields are renamed

• Required for API integration use cases

Back to the task at hand. Our first rule would be filter_Category=Brand%20identity because “Brand identity” has a space in it and the URL encoding for spaces is %20. Our second rule would be filterContains_Project%20lead=Cameron%20Toth because both “Project lead” and “Cameron Toth” have a space in them.

• To combine the filter rules into a query string you use the & symbol. For example filter_Category=Brand%20identity&filterContains_Project%20lead=Cameron%20Toth.

• Then take your share URL, which in our case is: https://airtable.com/shrsa57bWpEecPtzp, and add a question mark ( ?) followed by your query string.

• So, our final URL with our filtering conditions would be https://airtable.com/shrsa57bWpEecPtzp?filterEquals_Category=Brand%20identity&filterContains>_Project%20lead=Cameron%20Toth.

• If your URL has a question mark already then that means it already has a query string. Make sure to remove the existing query string from your URL before adding a new one.

Understanding Multiple Values in URL Filters

URL filters have a specific behavior when the same parameter appears multiple times that's important to understand:

• Single Filter with Multiple Values - When you repeat the same parameter name, Airtable creates a single filter with multiple values:

  • ?filter_Tags=Design&filter_Tags=Marketing

  • This means: Show records where Tags field matches "Design" OR "Marketing" (interpreted as one filter checking for either value)

  • Breakdown:

    • Not two separate filters

    • One filter with an array of values: ["Design", "Marketing"]

    • The filter checks if the field contains any of these values

    • Works like "is any of" for most field types

• Multiple Filters on Different Fields - To create separate filters on different fields, use different parameter names:

  • ?filter_Tags=Design&filter_Status=Active

  • This means: Show records where Tags is "Design" AND Status is "Active" (two separate filters)

• Combining Multiple Values with filterConjunction - Here's where it gets tricky - when you use filterConjunction=or with repeated parameters:

  • ?filter_Tags=A&filter_Tags=B&filterConjunction=or

  • You might think: Show (Tags = A) OR (Tags = B)

  • What actually happens: Single filter checking if Tags is any of [A, B]

  • Key point: The filterConjunction=or affects how multiple different field filters combine, not how multiple values for the same field work.

Here are some practical examples to better understand this:

• Example 1: Multiple Select Field

  • Goal: Show records with either "Marketing" or "Sales" tag

  • ?filter_Tags=Marketing&filter_Tags=Sales

  • This creates one filter checking for either value. Works as expected!

• Example 2: Multiple Conditions

  • Goal: Show records where (Status is "Active") OR (Priority is "High")

  • ?filter_Status=Active&filter_Priority=High&filterConjunction=or

  • This creates two filters with OR between them. Works as expected!

• Example 3: What You Can't Do

  • Goal: Show records where (Status is "Active" AND Priority is "High") OR (Status is "Completed" AND Priority is "Low")

  • ❌ Not possible - URL filters don't support grouped conditions or complex boolean logic

  • Alternative: Create separate views for each condition combination, or use Interface Designer with advanced filtering.

This behavior is especially important for:

• Multiple select fields - Repeated values work naturally

• Single select fields - Only first matching value matters

• Text fields - Will match any of the provided values

• Number fields - Will match any of the provided values

Remember: Repeating a parameter creates one filter with multiple values, not multiple filters. Use filterConjunction=or to change how different field filters combine, not how multiple values for one field work.

Supported URL filter operators

Note

Using the generic filter_ operator will typically yield the same result as the  filterEquals_ operator's output. However, by using filter_ Airtable will do its best to choose a filter that makes sense for the field you are filtering values by.

• For example, in multiple select fields, the filter_ operator would function more like the filterHasAnyOf_ operator. This would lead to a filter where if the field "has any of" the values set, then the records containing those values would be shown in the shared view.

• We strongly recommend using the filter_  or filterContains_ operator in almost all instances since multiple (separate) values cannot be encoded after filterIsAnyOf_, filterIsNoneOf_, filterHasAnyOf_, or filterHasAllOf_. In those cases, you’ll want to repeat the filter_ operator multiple times separated by “Or” operators as outlined in the next section.

The following filter operators can be used when constructing a custom share view URL:

• filter_

• filterEquals_

• filterNotEquals_

• filterContains_

• filterNotContains_

• filterGreater_

• filterGreaterOrEqual_

• filterLess_

• filterLessOrEqual_

• filterIsAnyOf_

• filterIsNoneOf_

• filterHasAnyOf_

• filterHasAllOf_

• filterEmpty_

• filterNotEmpty_

Note

The filterEmpty_ and filterNotEmpty_ operators do not require a value. Simply specify the field name:

• ?filterEmpty_Status

• This checks if the Status field is empty. Adding a value (e.g., ?filterEmpty_Status=true) has no effect—the value is ignored.

Using the "Or" operator between filters

When creating an encoded URL you will use the & symbol to combine multiple filters together as outlined in the example above. However, there may be times when you would rather filter records with the "Or" conjunction rather than the "And" conjunction. In these cases, you'll add the string &filterConjunction=or to the end of the encoded URL. So, using our use case above:

• If we modified the URL to be: https://airtable.com/shrsa57bWpEecPtzp?filterEquals_Category=Brand%20identity&filterContains_Project%20lead=Cameron%20Toth&filterConjunction=or

• Then, any records in the view equaling "Brand identity" in the category field or containing "Cameron Toth" in the Project lead field would be shown.

In this way, each And conjunction in the resulting URL is modified to be an Or conjunction instead.

Note

Using the filterConjunction=or string in an encoded URL is all or nothing. This means that there is no way to create a mix of And and Or conjunctions between filters.

FAQs