Most filmmakers lose time on the same task each month. You hunt for festivals, read rules, check dates, and guess what fits your film. You also track replies in a messy mix of tabs, emails, and notes.
TMFF keeps this simple on its side. TMFF curates monthly selections, runs an online film festival and screenplay contest, and hosts a watchable archive of 3500+ films. TMFF also states it earns trust from 15,000+ filmmakers. You can use that kind of clear, repeatable system for your own festival plan.
This article shows a lean way to collect festival data, keep it fresh, and act on it. You do not need a big team. You need a small pipeline, strict rules, and a bias for clean notes.
Start with the data that affects acceptance
Festival research fails when you track the wrong fields. Titles and logos do not help you decide. Rules, fit, and timing decide.
Rules and fit signals
Track runtime caps, format needs, and first-run rules. Track premiere terms with exact words from the page. Note genre and tone prefs when a fest states them. Also track what the fest shows, not just what it claims. TMFF’s archive and monthly picks show clear taste cues. Many festivals offer past winners, staff picks, or a catalog you can scan.
Deadlines and money
Track open dates, final dates, and fee tiers. Record the currency and whether fees change by date. Add a note for waiver rules if the fest posts them. Fees and dates change often. Your pipeline must re-check key pages on a set beat. If you do not re-check, your sheet turns into bad advice.
Build a lightweight scraping workflow you can run weekly
You can run a simple crawler with Python, Node, or a no-code tool. Keep the scope tight. Pull only what you need for a submit call. Start with one source per festival. Use the rules page, the submit page, and the dates page. Fetch HTML, parse the fields, and store the raw text for audits.
Sites rate-limit quick, repeat hits. Use a small pool and slow your pace, or your job will fail mid-run. Many teams use high-speed datacenter proxies.
Next, add change checks. Store a hash of each page segment that holds dates and rules. When the hash flips, flag the row and review it by hand.
Pick the right proxy type for festival sites
Proxy choice affects cost, speed, and risk. Festival sites vary a lot. Some run on simple CMS setups, while others sit behind strict bot tools.
Datacenter vs residential in plain terms
Datacenter IPs run fast and cost less. They fit tasks like re-checking the same public rules pages each week. They may trigger blocks on sites that watch for bot-like traffic.
Residential IPs blend in more. They cost more and run slower. They help when a site blocks most server IP ranges.
Control blocks with behavior, not brute force
Start with low request rates and steady gaps. Rotate user agents, but keep them real. Cache pages and avoid re-downloading assets like images and video.
Use a headless browser only when the page needs script to show dates or rules. Headless runs slow and breaks more often. HTML fetch plus parsing beats headless in most cases.
Stay compliant and protect your rep
Filmmakers work in a trust market. You should treat festival sites the same way you want festivals to treat your work. Follow site terms and robots rules where they apply to your use.
Collect public facts, not private data. Do not scrape emails, phone lists, or staff data for spam. Keep your goal narrow: rules, dates, fees, and public past-program data.
Respect load. Set hard caps on requests per host per hour. Add backoff on errors, and stop on repeated blocks.
Keep an audit trail. Store the page text you parsed and the time you pulled it. When a fest disputes a detail, you can fix your record fast.
Turn your dataset into better submissions
Data does not replace taste. It helps you aim your taste at the right target. Use your sheet to filter fast, then watch and read to confirm fit.
Use TMFF as a model for fast study. You can review past monthly selections and scan the 3500+ film archive for pacing, tone, and craft cues. You can do the same with other festivals that show past programs.
Build a simple submit log. Track what you sent, when you sent it, and what cut you used. Add notes on feedback, even when you get a no.
Over time, you will spot patterns. You may find that certain runtime bands or genres perform better for you. That insight helps you cut trailers, pick tags, and plan your next draft with intent.
You may also like:
Leave a reply