Content Recap - Dossier
The investigative sibling of Content Recap, built the opposite way: a 29-second 9:16 dossier on one near-black ground instead of two, IBM Plex Sans and Mono instead of a serif, and copy top-anchored against a four-cell index instead of centred in air. Seven scenes: a masthead carrying the publisher slab, headline and an 888×480 exhibit plate; the hero image whole for a beat; the four findings numbered by an index row whose active cell is a solid acid-yellow block; and a single inverted yellow close - the only bright frame in the video - with a QR tile and the article URL. Type is set larger than v1 at every length because the copy hangs from a fixed line rather than floating, so the first line always lands in the same place and a long finding simply fills more of the frame. Payload-compatible with Content Recap: the same nine variables (headline, hero_image, point_1 through point_4, publication_name, article_url, qr_image), so the same RSS or CMS-webhook row renders through either look - pick this one when the piece is a finding rather than a phrase, for investigations, warnings, and security or policy reporting.
- Aspect ratio
- 9:16 · Vertical
- Duration
- ~29s
- Category
- Social Media
What you can customize
This template exposes 9 dynamic fields you can swap per video — edit them in the editor or pass them to the API to batch-render variations at scale.
Publication Name
ChongLuaDao
Headline
Cybercrime gangs are bypassing bank security using unauthorized tools on Telegram
Hero Image
https://images.unsplash.com/photo-1594521870728-a988b3fc4d99?fm=jpg&q=80&w=1080&h=1660&fit=crop&crop=faces
Point 1
Twenty-two Telegram channels sold the tools.
Point 2
Virtual camera tools inject a photo, video, or deepfake in place of the phone’s real camera feed — and the bank sees a live face.
Point 3
Virtual camera attacks in 2024 were more than 25 times higher than in 2023.
Point 4
Victims’ money lands in leased bank accounts — “water houses” — where launderers use the bypass tools to move it out within seconds and convert it to Tether before anyone can freeze the account.
Qr Image
https://api.qrserver.com/v1/create-qr-code/?size=600x600&margin=0&color=0B0E12&bgcolor=F2E85C&data=https%3A%2F%2Fchongluadao.vn%2Fblog%2Fen%2F2026%2F07%2Fcac-bang-nhom-toi-pham-mang-dang-qua-mat-bao-mat-ngan-hang-bang-cong-cu-trai-phep-tren-telegram%2F
Article Url
chongluadao.vn/blog
Frequently asked questions
How do I customize the Content Recap - Dossier template?
Open the template in the Renderly editor and replace its 9 customizable fields (such as Publication Name) with your own text, images, or video. Every change previews instantly before you render.
How much does it cost to render this template?
Rendering is credit-based — 1 credit equals 1 minute of 1080p video. You only pay when you export, and credits never expire on the pay-as-you-go plan.
Can I generate this video at scale via the API?
Yes. Mark any field as a dynamic variable and call the Renderly API (or a no-code integration like Zapier) with a JSON payload to batch-render a unique video for every row of data.
More Social Media templates
Daily Special Card
A 20-second vertical (9:16) Story card for a neighbourhood restaurant's dish of the day: what it is, what is in it, what it costs, and how long it is on. It expires in 24 hours, which is the point - one venue renders 365 of these a year, and a chain multiplies that by every location. Wire it to the POS or a "special of the day" row so a render fires each morning and the MP4 lands in Stories before service. Six scenes: a chalk menu board that establishes venue and date while the plate rises into frame, the dish full-bleed for the appetite beat, the ingredients set like a menu line beside a taped-in print, the price once and big and immediately qualified by how long it is on so value reads as scarcity rather than discount, a paper card laid over a dim pass shot, and a close on the venue wordmark above a green band. The photo treatment is the part that does the work: a line cook shoots one plate on a phone in a dim kitchen, so every image is either matted in paper at a slight rotation or sitting behind a fixed four-stop scrim with exposure normalised and a warm radial putting candlelight back into a flat exposure, and the template - never the venue - chooses the crop. Board and paper grounds alternate scene to scene against a single green accent, set in Instrument Serif, Geist and JetBrains Mono. Twelve dynamic fields: dish_photo_1 plus optional dish_photo_2 and dish_photo_3 (fall back to dish_photo_1 when the venue supplies one shot - the three slots are cropped differently, so reuse does not read as repetition), dish_name, dish_description, price, availability, date_label, venue_name, venue_address, and the two composite lines venue_date_line and venue_address_line that scenes 02 and 05 set as a single run. Pass price preformatted with its currency symbol ($24, 19 EUR) and keep it to four characters at the 340px size. Length ceilings: dish_name about 34 characters, dish_description about 78 (three lines - the block is pinned between a rule and the footer, so a fourth line clips), availability about 40. The venue logo is deliberately not a variable: it is the same mark on every render for a single restaurant or a chain, so swap it once per brand.
Content Recap - Photo Plate
The photo-led sibling of Content Recap, for pieces that arrive with an image library. A 31-second 9:16 recap where a photograph fills every single frame and the writing sits on an inset chalk plate laid over it, bottom-anchored at a fixed line so only its top edge moves: short copy leaves three-quarters of the picture visible, a long pull leaves a third, and the photograph simply donates the space. Seven scenes: a cover carrying the headline under a deep-green category kicker, the four points each paired with their own picture and numbered 01-04, a full-bleed 2x2 contact sheet at the midpoint that is nothing but photography, and a close where the image drops to grayscale so the QR tile is the only thing competing for attention. Instrument Serif set dark on chalk rather than light on ink, a four-segment progress rule instead of a counter, and the deep green used exactly three times in the whole video, never on a photograph. Twelve variables: the nine that v1 and v2 already take (headline, point_1 through point_4, publication_name, article_url, qr_image, hero_image) plus image_1, image_2 and image_3, so the same RSS or CMS-webhook row renders through any of the three looks once the scraper also pulls the first three in-body images. Nothing is used once - the hero opens the video, returns in the contact sheet, and comes back tighter-cropped on the last point. Pick this one when the piece has real photography behind it; pick v1 or v2 when it does not, because this template has nowhere to hide a missing picture.
Content Recap - Written Piece to Video
An editorial, deliberately quiet 34-second 9:16 recap of a single written piece - a blog post, newsletter issue, or press release turned into a Reel/Short. Seven scenes on an ink → photo → newsprint → ink rhythm: a title-page cover carrying the headline, one held hero image on a solid ink caption band, the four points that matter as full-page pull-quotes numbered 01–04 in cobalt, and a scannable close with a QR tile and the article URL. Newsreader serif for every word pulled from the piece, JetBrains Mono for all furniture, and a single cobalt accent used exactly four times in the whole video. Built for messy input: each text slot is a fixed box with a type ladder, so a six-word point and a twenty-five-word point both look set on purpose. Swap the seven per-post fields - headline, hero_image, point_1 through point_4, article_url and its qr_image - while publication_name is bound once per publisher, so an RSS item or CMS publish webhook renders a finished video per post and the same payload shape backfills an entire archive.