BugWP logo BugWP
Back to Community
Home / Community / Plugin → Flamingo

Why Flamingo Doesn't Show File Attachments and How to Work Around It

29 threads Sep 16, 2025 Plugin → Flamingo

Content

If you're using the Flamingo plugin to store Contact Form 7 submissions, you've likely encountered a common point of confusion: uploaded files appear only as a filename or a hash token, with no way to view or download the actual attachment. This article explains why this happens and explores the most common solutions discussed by the community.

The Core Issue: Flamingo Does Not Store Uploaded Files

Based on numerous user reports and direct responses from the Flamingo team, the plugin's design is very clear on this point: Flamingo does not save uploaded files to your server or database. It is designed solely to store the text-based metadata from form submissions, such as names, email addresses, messages, and the names of any files that were uploaded.

When you see a file reference like "example-home.jpg" or a hash token like "939ea8182c455e53789743a9dad954a2" in an inbound message, that is the extent of the information Flamingo captures. The actual file content is not stored by the plugin.

Why Doesn't Flamingo Store Attachments?

The Flamingo team has consistently cited two primary reasons for this design decision:

  1. Security: Allowing file uploads from anonymous site users presents a significant security risk. Malicious actors could attempt to upload executable files, scripts, or other harmful content to compromise your website.
  2. Privacy: Storing files containing personal data (like CVs, identification documents, or photos) creates privacy concerns and may conflict with data protection regulations, depending on your location and how the data is handled.

This behavior is consistent with Contact Form 7 itself, which moves uploaded files to a temporary folder only for the purpose of attaching them to the email, after which they are deleted.

Common Community Solutions and Workarounds

Since this is a limitation of Flamingo's core design, solutions involve using additional plugins or custom code. Here are the most frequently mentioned approaches from the community:

1. Use a Complementary Plugin

Many users have successfully resolved this by installing a separate plugin designed to handle CF7 file uploads. These plugins save files to your server's uploads directory or media library. Popular options mentioned in the threads include:

  • Store file uploads for Contact Form 7: A free plugin that saves uploaded files to the WordPress media library.
  • CF7 Submissions: Another plugin that stores both form data and attachments.
  • Storage for Contact Form 7: A premium plugin available on CodeCanyon.

Note: While these plugins save the files, they may not always integrate directly with the Flamingo admin screen. You might need to access the files through the other plugin's interface or your media library.

2. Custom Code Workaround

For developers, one suggested workaround is to use a hidden field in your Contact Form 7 form to capture the file URL after it is uploaded. This URL can then be stored as text within the Flamingo message, providing a clickable link. This requires custom code to hook into the form submission process and handle the file upload before CF7 deletes it.

3. Rely on Email Attachments

The simplest method is to ensure your Contact Form 7 email templates are correctly configured to include the uploaded file as an attachment. This way, the file is delivered directly to your inbox, which acts as your primary storage method, while Flamingo serves as a text-based backup of the submission details.

Conclusion

The inability to view or download file attachments directly within Flamingo is not a bug but a deliberate design choice focused on security and privacy. While the Flamingo team has shown no indication of changing this functionality, the WordPress community has developed several effective workarounds. Your best options are to use a dedicated file storage plugin for Contact Form 7 or ensure your email settings are configured to receive attachments directly.

Related Support Threads Support