Discord to Telegram Photos Missing? Filters vs Cleaner

If a Discord-to-Telegram route delivers plain text but a notice with a picture is missing, or arrives without the picture, check the task’s Filters and Cleaner separately. In RedFox Auto Forward Discord To Telegram (D2T), a green FILTERS PHOTOS or FILTERS PHOTO WITH TEXT switch skips matching messages, while a green CLEANER PHOTO switch removes images from messages. The first can make the whole notice disappear; the second is documented as removing the image itself. Fresh controlled posts help prioritize these checks; a before-and-after result is needed before applying a change to the live task.

This guide is for an operator whose existing D2T task already delivers ordinary text and who wants the intended photos back without switching off every rule on the account. The checks below are a reader-run diagnostic, not a test run by Auto-Bot.io. RedFox supplies the product; Auto-Bot.io publishes this editorial guide. Product documentation was checked on October 26, 2026. The featured image is a concept illustration, not product UI or a tested result.

1. A green photo switch can do two different things

D2T’s Filters guide and Cleaner guide use the same toggle language: a green check (✓) turns the rule on and a gray cross (✕) leaves it off. What the rule does once it is on is not the same:

A Filters match means the message is skipped. Nothing in the docs says its text is then forwarded on its own, so do not expect the original caption to survive a skip. A Cleaner match removes the picture from the message rather than skipping the message. The docs also do not say which of the two runs first, or what a message looks like when Cleaner removes its only content, so do not reason from order. Change one switch at a time and read a fresh result.

2. Classify what actually arrives

Use one recent notice and its Telegram copy. RedFox’s D2T site lists image, video, audio and document forwarding, so a healthy route can carry pictures; the next step is to distinguish saved content rules from a source-form or delivery problem.

• Text posts arrive, but the picture notice never appears: the whole message may have been skipped. Check Filters first, then the task’s Blacklist and Whitelist, because a keyword in the notice’s own text can exclude it too.
• The notice’s text arrives, but the picture does not: look at Cleaner, starting with CLEANER PHOTO.
• Nothing new arrives, including plain text: first check that the text itself is permitted by the task’s rules. If fresh permitted text still fails, check task status and exact endpoints with the D2T setup guide.
• Only a link card or an uploaded file is missing: that may not be a photo at all. See the link-preview guide for cards; files have their own FILTERS DOCUMENT and CLEANER DOCUMENT switches.

“An image in the channel” is not one thing. Discord’s message reference keeps uploaded attachments and embedded content in separate fields, and embeds include several types. The D2T docs do not say how each Discord form becomes a Telegram photo, a document or a preview, so test the form your notices actually use instead of assuming.

If your source is Telegram, use the Telegram photo-caption guide. If the destination is another Discord channel, use the Discord-to-Discord attachment guide.

3. Open the one task and record its state

Open the task that produces the Telegram copy. The task-settings guide shows Source (the Discord channel ID), Target (the Telegram chat ID) and an optional topic on the task detail page. Filters and Cleaner open from that page, each with a status line showing how many rules are active. Prefer D2T Web, the iOS app or the Android app; choose the surface you like. Before changing anything, record:

• The exact source and target, and whether any other task sends to the same Telegram destination.
• Forwarding Status, which should read RUNNING.
• Filters: PHOTOS, PHOTO WITH TEXT, ALBUM, DOCUMENT and LINK, each green or gray.
• Cleaner: PHOTO, PHOTO WITHOUT TEXT, TEXT, DOCUMENT and URL PREVIEW, each green or gray.
• The active Blacklist, Whitelist and Replace rules: their conditions, sender restrictions and task associations, not only their counts.

D2T’s plan table lists the Cleaner Filter for Diamond and Platinum, not Gold. Confirm that the Cleaner section is available on your account before relying on that branch. Keep the note private: do not publish channel IDs, invite links or screenshots that show account details.

4. Send fresh specimens through a controlled task

This is a reader-run check, not a test performed by Auto-Bot.io. Use a private Discord channel you control and a private Telegram destination, with a task whose Filters and Cleaner switches match the live one. Do not send test images to your live audience. The official not-forwarding guide recommends isolating a simple, clean test setup when the rules do not explain a failure. This guide recommends confining its disable-all tip to that isolated test, not a live account. Create the test task as the setup guide describes, set the switches by hand, then save and reopen the task to confirm them.

Before interpreting the specimens, record which other rules actually apply to the test task. Choose typed wording and a sender that satisfy the intended Whitelist and avoid the Blacklist; keep that wording consistent apart from a fresh identifier that does not change those matches. A captionless specimen cannot establish photo cleaning if a required text condition already makes it ineligible. Keep any isolation changes confined to this test task, and do not use Apply For All Tasks. First check whether the saved test configuration reproduces the relevant missing-photo pattern; if it does not, do not infer a live-task fix from it.

Use pictures you created or may share. Use a fresh identifier that preserves the intended text-rule matches and a new picture for every run, and wait through any configured delay, so duplicate or delay settings and old copies do not blur the result. Adapt the example wording to your recorded eligibility conditions, then post these as separate new messages in the Discord test channel:

1. Specimen A, text control: “PHOTO CHECK A — text only.”
2. Specimen B, picture only: upload one small harmless image with no typed message. Put a large letter B on the picture so you can tell it apart.
3. Specimen C, picture with text: upload another small image with a large letter C and type “PHOTO CHECK C — picture with text” in the same Discord message.
4. Specimen D, your real form (optional): use it only if your real notices differ from B and C: a pasted image link that Discord previews, an uploaded file such as a PDF, a bot embed, or several images in one message. Send one harmless example marked “PHOTO CHECK D.” The docs list FILTERS ALBUM separately, so a multi-image notice is its own specimen.

For each specimen, note the Discord message reference, send time, task, switch states and what arrived: text, picture, both or neither. “C: text arrived, picture absent” is far more useful than “media broken.”

5. Read the pattern, then change one switch

• A arrives; B and C are absent. Check FILTERS PHOTOS and other applicable exclusions. CLEANER PHOTO may also be relevant, but the docs do not establish what happens when cleaning leaves no content. This pattern alone does not distinguish exclusion, cleaning and failed media delivery.
• A and B arrive; C is absent. Check FILTERS PHOTO WITH TEXT and C’s actual text-rule eligibility.
• A arrives; C’s text arrives without its picture. Start with CLEANER PHOTO, then compare a fresh result after one controlled change. The appearance alone does not prove Cleaner caused it.
• A and C arrive complete; B is absent. Check CLEANER PHOTO WITHOUT TEXT, but first rule out a text requirement that B cannot satisfy.
• C’s picture arrives without its typed text. Check CLEANER TEXT and other configured content changes.
• A, B and C arrive complete. These particular specimens pass. Compare the real notice’s wording, sender and form; this does not clear every ordinary upload.
• B and C arrive, but D does not. Follow D’s actual form: inspect document controls for files and link/preview controls for links. Do not infer how arbitrary embeds are mapped.
• A is also absent. Check whether A itself is excluded or cleaned, then verify task status and endpoints. If fresh permitted text also fails, return to the base-route guide.

If two rules could explain the same result, for example a Filters photo switch and CLEANER PHOTO are both green, change only the one that matches the policy you can justify. Save, reopen the task and send a fresh specimen again. Do not stack unexplained changes. Anything that fits no row is a result to keep, not a reason to loosen more switches.

6. Restore the intended photos, not an unfiltered feed

First decide what the feed should do with photo notices. If you meant to drop pictures, the switch is working and nothing needs repair. If you meant to keep them, restore only the switch the specimens implicated:

1. Change one switch on the controlled task. Set the implicated switch to gray (✕), then save and reopen the task to read the state back.
2. Send fresh B and C, and D if you used it. Confirm that the previously failing permitted specimen now arrives with its intended picture. Also verify that a specimen your retained rules should reject remains excluded. If the change does not explain the difference, restore the recorded switch value and investigate the next relevant condition; do not stack unexplained changes.
3. Apply the verified adjustment to the live task only after that comparison succeeds. Choose a quiet moment, retain the before-state for rollback, and verify a fresh permitted post and the intended exclusion on that task. An unexplained or still-failing test is not a reason to change production.

If you want captioned pictures but not captionless ones, the docs list CLEANER PHOTO WITHOUT TEXT and FILTERS PHOTO WITH TEXT as separate switches. Test what your destination actually receives instead of inferring the outcome from the names. Do not switch off every Filters and Cleaner rule on the account, and do not delete and recreate a task to fix one picture rule. A change on one task says nothing about other tasks and does not promise that earlier skipped notices will be replayed, so judge only new posts.

Pictures in a real notice may belong to someone else. Keep any source credit your community requires and confirm that you may republish them to the Telegram audience; a routing rule does not grant redistribution rights.

If the controlled result still contradicts the saved switches, keep a short private record: the switch states, which specimens arrived, and the times. The official guide asks for a clean test setup that support can inspect. Offer harmless channels you created for that purpose, never your live community, a token or a password.

RedFox’s runtime FAQ says you do not need to keep your internet on for the bot to copy messages, so leaving a management screen open is not a fix for a missing picture. Once pictures arrive, the media readability guide covers whether the result still reads well on Telegram.

FAQ

Does FILTERS PHOTO WITH TEXT keep the text and drop only the picture?

The docs describe it as skipping photos with accompanying text. They do not describe the text being forwarded alone, so expect the whole message to be skipped, and confirm with Specimen C. Removing only the picture is what Cleaner is documented to do.

Is text printed inside a picture the same as the text I type with it?

Do not assume so. Specimen C uses text typed in the Discord message next to the upload. Words drawn inside the pixels are image content, and the docs do not say that they count as accompanying text.

Should I turn every rule off to find the cause?

Not on a live account. Use an isolated test task, as the official troubleshooting guide suggests, and change one switch per run. Turning everything off can hide the cause and send content to your audience that you meant to exclude.

Will the change bring back notices that were already skipped?

Do not assume it will. Verify new source posts after the change; recovering older notices is a separate decision for the destination’s administrators.

Find the one rule, keep the photo notice

Pick one existing task, record its Filters and Cleaner switches, run the three or four specimens in a private test route, and change only the switch the pattern implicates. Explore RedFox Auto Forward Discord To Telegram, then manage the task in D2T Web, iOS or Android. Choose your preferred surface; Web or the apps give you the management interface for reviewing the task and its content rules. The useful result is not a different setting but a fresh picture notice that arrives the way you intended.