Using Filters

For a finer grained control over what kind of messages will be allowed or not in your callback functions, you can use Filters.


This page makes use of Handlers to show you how to handle updates. Learn more at Update Handling.

  • This example will show you how to only handle messages containing an Audio object and ignore any other message:

    from pyrogram import Filters
    def my_handler(client, message):
  • or, without decorators:

    from pyrogram import Filters, MessageHandler
    def my_handler(client, message):

Combining Filters

Filters can also be used in a more advanced way by inverting and combining more filters together using bitwise operators:

  • Use ~ to invert a filter (behaves like the not operator).
  • Use & and | to merge two filters (behave like and, or operators respectively).

Here are some examples:

  • Message is a text message and is not edited.

    @app.on_message(Filters.text & ~Filters.edited)
    def my_handler(client, message):
  • Message is a sticker and is coming from a channel or a private chat.

    @app.on_message(Filters.sticker & ( | Filters.private))
    def my_handler(client, message):

Advanced Filters

Some filters, like command() or regex() can also accept arguments:

  • Message is either a /start or /help command.

    @app.on_message(Filters.command(["start", "help"]))
    def my_handler(client, message):
  • Message is a text message matching the given regex pattern.

    def my_handler(client, message):

More handlers using different filters can also live together.

def start_command(client, message):
    print("This is the /start command")

def help_command(client, message):
    print("This is the /help command")

def from_pyrogramchat(client, message):
    print("New message in @PyrogramChat")

Custom Filters

Pyrogram already provides lots of built-in Filters to work with, but in case you can’t find a specific one for your needs or want to build a custom filter by yourself (to be used in a different handler, for example) you can use Filters.create().


At the moment, the built-in filters are intended to be used with the MessageHandler only.

An example to demonstrate how custom filters work is to show how to create and use one for the CallbackQueryHandler. Note that callback queries updates are only received by Bots; create and authorize your bot, then send a message with an inline keyboard to yourself. This allows you to test your filter by pressing the inline button:

from pyrogram import InlineKeyboardMarkup, InlineKeyboardButton

    "username",  # Change this to your username or id
    "Pyrogram's custom filter test",
        [[InlineKeyboardButton("Press me", b"pyrogram")]]

Basic Filters

For this basic filter we will be using only the first two parameters of Filters.create().

The code below creates a simple filter for hardcoded callback data. This filter will only allow callback queries containing “pyrogram” as data:

hardcoded_data = Filters.create(
    func=lambda filter, callback_query: == b"pyrogram"

The lambda operator in python is used to create small anonymous functions and is perfect for this example, the same could be achieved with a normal function, but we don’t really need it as it makes sense only inside the filter itself:

def func(filter, callback_query):
    return == b"pyrogram"

hardcoded_data = Filters.create(

The filter usage remains the same:

def pyrogram_data(client, callback_query):
    client.answer_callback_query(, "it works!")

Filters with Arguments

A much cooler filter would be one that accepts “pyrogram” or any other data as argument at usage time. A dynamic filter like this will make use of the third parameter of Filters.create().

This is how a dynamic custom filter looks like:

def dynamic_data(data):
    return Filters.create(
        func=lambda filter, callback_query: ==,
        data=data  # "data" kwarg is accessed with ""

And its usage:

def pyrogram_data(client, callback_query):
    client.answer_callback_query(, "it works!")