Telegram Photos Not Forwarding? Check Caption Filters

If text posts arrive but Telegram photos or captions disappear, check the task’s type filters and Cleaner before reconnecting the account. In RedFox Auto Forward Telegram, turning a type filter on excludes that kind of message. Photo Only excludes photos without captions; Photo With Text excludes captioned photos. Cleaner is different: it removes content rather than selecting which whole posts should pass. A missing post and a delivered post with missing content need different checks.

This guide is for an existing Telegram-to-Telegram route that already delivers some messages. You will use a small set of owned test posts to separate a photo-type exclusion, a content-removal rule and a route-wide problem—without loosening every rule on a live audience.

Product identity: RedFox Auto Forward Telegram uses @AutoForwardNew_Bot. The previous bot has moved to this current handle. Auto-Bot.io is an editorial publisher, not the developer or operator of the product.

The featured artwork is a conceptual illustration of filtering versus cleaning, not a Telegram or Auto Forward screenshot. The workflow below is a source-backed diagnostic plan, not a claim that we reproduced a customer incident.

Start with the missing part, not the account connection

“The photo did not forward” can describe three different outcomes. Open the source and destination side by side and identify which one you actually have.

This is a triage order, not a verdict about a particular failed message. A photo can also encounter a sending error. If an unfiltered controlled sample still fails, keep the error and sample details rather than repeatedly switching filters.

RedFox’s Filter By Type guide explicitly distinguishes skipping entire messages from Cleaner’s content removal. That distinction is the fastest useful starting point when only part of your feed is affected.

Photo Only is an exclusion—not “forward only photos”

The switch names describe what the rule removes. They are not an allow-list of the formats you want to receive. According to the official type-filter documentation:

• Photo: excludes photo messages.
• Photo Only: excludes photos with no text or caption.
• Photo With Text: excludes photos that carry a caption.
• Album: excludes grouped photo/video media.
• Document: excludes file messages, such as a PDF or DOCX.

If you enabled Photo With Text because you wanted image announcements with a caption, you selected the opposite behavior. For a captioned-photo feed, leave that exclusion off. If your policy is specifically to reject standalone captionless photos, Photo Only is the relevant exclusion to evaluate—not the broader Photo switch.

Turning one exclusion off does not override the rest of the task. A link filter, blacklist, whitelist or another active condition can still keep the post out. Do not diagnose a photo setting from a single caption containing a URL and a blocked word; begin with plain, distinctive test text.

Also separate a real caption from words printed inside the picture. Telegram’s Message documentation defines photo media and a caption as separate fields. A poster reading “RELEASE” inside its pixels is not automatically a captioned photo. Inspect the source post itself: does it have selectable text attached to the image, or only lettering in the image?

Build a small specimen set in chats you control

Use an owned source and a private test destination, with harmless media you have permission to share. Preserve your live task’s current settings first. If you already have a controlled test task, use it; otherwise follow the existing setup guide rather than rebuilding the live route in the middle of diagnosis.

The following is a fictional test set. Its labels help you identify exactly what arrived. Send each as a new source post after the test task is active; do not use repeated retries of the same old message as your only evidence.

Keep a short record: source sample label, posting time, task label, current rules, destination result and any visible error. “C image present / caption absent” is much more useful than “media broken.” Sample D matters because the visual content of a file can look like a photo while the source message uses a different media type.

First run the set with the controlled task’s photo-type exclusions and photo-removal Cleaner settings disabled. Isolate any other active rules that would reject your harmless samples. This establishes a base result for that task; it does not authorize removing protections from production or guarantee all future media delivery.

Change one rule and read the result

Open the affected test task and its Filters section. Check the type filters separately from the Cleaner tab. The Cleaner guide documents opening the task, locating Filters and then selecting Cleaner; the type-filter guide documents enabling exclusions in the Filters tab.

1. Record the original switch values. Include the broad Photo setting, both caption-specific settings, Album, Document, and any relevant Cleaner option. Your rollback should be a known configuration, not a guess.
2. Change only the rule that matches the symptom. If captioned single photos are entirely missing, turn off Photo With Text on the test task while leaving the rest of your controlled baseline unchanged.
3. Send a fresh matching sample and a control. Use a new captioned photo and a fresh text post. Then compare image presence, caption presence and whole-post presence.
4. Confirm the intended rejection still works. If your goal is “keep captioned photos, reject captionless ones,” test another new captionless photo with Photo Only enabled. A useful filter test checks both sides of the policy.
5. Restore or keep the change based on the observed result. If it did not explain the difference, restore the previous value and move to the next relevant rule. Do not stack unexplained changes.

For an album, check Album and the broad Photo setting as well; test it as its own source format. If the group arrives but its items are split or intermittently missing, that is a different question. Our Album Delivery Modes guide owns the Fast/Balanced/Stable/Careful decision. A slower delivery mode is not a substitute for removing an intentional exclusion.

Use the controls your plan includes. The current RedFox site, checked October 9, 2026, distinguishes basic Free routing from paid advanced filters and offers Trial Platinum for eligible new users. Do not assume basic Free routing includes every rule discussed here; confirm your account’s active plan and available controls before configuring the test.

Ready to inspect one route? Open the RedFox Web App, select your controlled task and compare Filters with Cleaner. Start with the missing part of the message—not a new account connection.

When the caption survives but the photo does not

If the destination contains your caption but not the image, begin with Cleaner → Photo and related photo-removal options. RedFox describes Cleaner as removing unwanted content; it is not the same operation as blocking a whole post. On the controlled task, disable the relevant photo-removal option, then send a new captioned-photo sample and compare the result.

The reverse case needs a text/content check. If the image is present but the caption has changed, inspect Cleaner and any other modifications configured on that task. A removed URL preview, a removed URL and a removed photo are different outcomes. The official Cleaner guide gives separate URL Preview and URL examples: hiding a preview is not the same as removing the link text, and stripping the URL is not a way to preserve an important action link.

Do not add a replacement caption or header just to make the test appear successful. Your objective is to identify the original removal. Keep a short “before → after” note, then use the existing headers, footers and Cleaner guide for intentional presentation changes once the diagnostic is complete.

Check content rules without changing every task

If the type settings look right but the entire post still disappears, inspect active whitelist and blacklist rules for the specific task. A required word that appears only inside the image is not evidence that the actual caption matches your text rule. Check the real source wording, rule type and intended scope; do not assume image text recognition is part of an ordinary word filter.

Both rule guides document Activate/Deactivate For Task separately from Apply For All Tasks. Use the task-scoped control for this investigation. A global change could alter unrelated routes that were working correctly.

If the test is inconclusive, prepare a support packet with the task label, sample type, source/destination observations, enabled rule names, time and exact visible error. Remove private chat content and credentials. Stop retrying a live audience if the packet does not establish why the rule should change.

Restore the live policy—not a permanently unfiltered feed

Once a controlled change explains the symptom, apply only that necessary adjustment to the intended live task. Verify a fresh permitted post and a fresh post that should remain excluded. Keep the former setting available for rollback. Do not clone the entire source history to prove a new-message filter change.

Manage RedFox from the official Web App, iOS app or Android app. Web/App is the recommended management path for fuller controls than the limited Telegram-bot entrypoint. Active forwarding tasks run in RedFox’s cloud, so the management interface does not need to stay open.

For the supported routing and rule overview, see Auto Forward Telegram. Use @AutoForwardNew_Bot if you enter through Telegram, and verify the exact handle rather than trusting a display name or avatar.