If you’ve spent any time working with e-commerce platforms, static site generators, or content management systems that power online stores, you’ve probably run into Liquid. It’s the templating language that powers Shopify, Jekyll, and a handful of other tools that turn raw content into something usable for shoppers, blog readers, and brand owners. As someone who’s spent the last seven years as a Liquid filter supplier—helping merchants and developers build clean, efficient, and tailored online experiences, I get asked one question more than any other: “How many built-in filters does Liquid have, anyway?” Liquid
It’s a fair question. Templating tools live or die by their ability to simplify content manipulation without forcing developers to write custom code from scratch. Filters are the workhorses of Liquid: they let you format prices, reorder strings, filter collections, and transform data with just a quick tag. But the answer isn’t as straightforward as a single number. Liquid’s core set of built-in filters has evolved over time, and there’s a big difference between the base core filters and the extended, platform-specific filters that tools like Shopify add on. Let’s break this down, straight from someone who works with Liquid filters every single day.
First, let’s define what a built-in filter is. At its core, a Liquid filter is a function that takes input (like a string, number, or array) and modifies it to fit a specific use case, without extra logic. For example, the upcase filter turns a string into all uppercase: {{ "hello world" | upcase }} becomes “HELLO WORLD”. The default filter returns a fallback value if the input is null or empty: {{ product.vendor | default: "Our Brand" }} fills in a name if a product listing forgot to add a vendor.
The base, open-source version of Liquid (the one that powers Jekyll, open-source static sites, and other self-hosted tools) has a set of filters that the project’s maintainers have standardized. As of 2024, that core set sits at 52 built-in filters. That number isn’t random; it’s been trimmed and expanded over decades of use to cover the most common tasks developers actually need, without bloating the language. Let’s run through a few of the most widely used core filters to put that number in perspective.
String manipulation filters make up about a third of those core 52, and they’re the most intuitive. There’s upcase and downcase for changing text case, capitalize to capitalize the first letter of every word, strip_html to remove unwanted markup from content, truncate to cut long text short (perfect for product descriptions on homepages), and slice to pull out specific characters from a string. If you’re building a blog, you’ll use truncate constantly to avoid long post previews stretching your layout. For product pages, strip_html is a lifesaver, turning messy raw text from product specs into clean, readable lines.
Next, number and math filters, essential for e-commerce. Core Liquid has plus, minus, times, and divided_by for basic arithmetic, though many developers skip those in favor of platform math, but there are also round to round numbers to a set decimal place, floor and ceil for rounding up or down, and money to format numbers as currency. That last one is especially important; it lets you turn a raw number like 29.99 into $29.99, with currency symbols tailored to the user’s location. As a supplier, I’ve seen merchants rely on that filter to avoid manually formatting every product price, saving hours of work.
Array and collection filters make up another big chunk of the core set, and they’re critical for organizing products, blog posts, and other content. There’s sort to order arrays by a specific attribute, map to extract a single property from every item in an array, where to filter items that meet a condition (like only showing products that are in stock), first and last to grab the start or end of a list, and size to count how many items are in an array. For store owners, where is game-changing: you can use {% assign in_stock_products = all_products | where: "inventory_quantity", ">", 0 %} to automatically pull only products that are available to sell, no manual sorting required.
Date filters round out the core set, perfect for timestamps on blog posts, order confirmations, or product launch dates. The core has date to format timestamps into human-readable text—so {{ product.published_at | date: "%B %d, %Y" }} turns a raw timestamp into “October 15, 2024”—plus time and timezone for adjusting times across regions.
Now, here’s where the number gets misleading for most users: if you use Liquid with a hosted platform like Shopify, BigCommerce, or Craft CMS, you’re not just using those 52 core filters. Each platform adds its own custom, built-in filters tailored specifically to their use case, and those add-ons almost always push the total number of available filters well over 200. As a Liquid filter supplier, this is a point I bring up with clients all the time: the “built-in” count depends entirely on which version of Liquid you’re working with.
Let’s use Shopify as an example, since it’s the most common platform for Liquid-powered e-commerce. Shopify adds over 170 platform-specific built-in filters on top of the 52 core ones, bringing the total to around 225 filters for Shopify users. Many of these are built exclusively for online stores, and they’re why most merchants don’t need custom filters. You’ve got price to format prices with region-specific tax rules, asset_url to pull the direct link to an image or CSS file stored in your Shopify theme, variant_title to format product option names (like “Size: Large”), and metafield to pull custom data stored for a product or customer. There’s even filters for things like shipping_price to calculate estimated shipping costs, product_reviews to pull review ratings, and money_with_currency to show both price and currency type, like “$29.99 USD”.
What’s interesting about these platform-specific filters is that they’re all built on top of the core Liquid framework. When I work with Shopify clients, I often explain that the core filters are the foundation, but the platform extensions are what make Liquid so powerful for e-commerce. For example, if you wanted to display a product’s discounted price, you don’t need to build a custom filter from scratch—Shopify gives you {{ product.variants.first.price | money_with_currency }} to handle that automatically. That saves developers hours of work and reduces the risk of bugs in custom code.
There’s a third layer here too, and it’s one that a lot of people miss: some filters that look like built-in filters are actually tags, or extensions added by third-party themes or apps. For example, if you see a filter like badges that adds a “Sale” or “New” tag to a product, that’s usually a custom filter added by a theme, not part of the core or official platform set. As a supplier, I also work with clients who build custom filters for their unique use cases, like a filter that converts product dimensions into a shipping label format, or one that translates product names into multiple languages. Those custom filters aren’t “built-in,” but they’re extensions that make Liquid even more flexible.
Now, why does this matter? If you’re a store owner or developer, knowing how many built-in filters Liquid has helps you avoid wasting time writing custom code for tasks that are already handled. For example, if you need to truncate a long product title, you don’t need to ask a developer to build a tool—there’s a core filter for that. If you need to format a date for a blog post, the date filter works across most platforms.
As someone who’s supplied Liquid filters for seven years, I’ve seen too many merchants overcomplicate things, trying to build custom filters for tasks that are already part of the standard set. On the flip side, I’ve also seen developers struggle to find the right filter when they’re working with a less common platform, where the number of built-in filters might be smaller than Shopify’s set. That’s why I always advise clients to check their platform’s official Liquid documentation first, before building anything custom.
Let’s wrap this up with a clear breakdown: if you’re using the open-source, base version of Liquid, you have 52 built-in filters. If you’re using a platform like Shopify, that number jumps to around 225, with the gap made up of platform-specific filters built for e-commerce. For other platforms, it falls somewhere in between—Jekyll, for example, has around 80 built-in filters, a mix of core and Jekyll-specific extensions.
If you’re looking to optimize your Liquid templates, streamline your store’s content, or even build custom filters tailored to your brand’s needs, I’m here to help. Whether you’re a small business owner just starting out, a developer looking to simplify your workflow, or a brand needing tailored filter solutions, we provide high-quality Liquid filter tools and support to fit your needs. To discuss your requirements, feel free to reach out to our team for a consultation.
Powders References
Shopify Liquid Documentation
Jekyll Liquid Documentation
Liquid Core Project GitHub Repository
BigCommerce Liquid Reference
Craft CMS Templating Documentation
Shenzhen Xinweitai Biotechnology Ltd.
As one of the most experienced liquid manufacturers and suppliers in China, we have world-leading production equipment and strong manufacturing capabilities. Please rest assured to buy bulk high quality liquid made in China here from our factory. Customized orders are welcome.
Address: 5A15, Shenzhou Computer Building, Madame Curie Avenue, Vanke City Community, Banqiao Subdistrict, Longgang District, Shenzhen
E-mail: info@vanayt.com
WebSite: https://www.vanayt.com/
