Chapter 36 — Further Reading

Delivery is the most spec-driven, fastest-changing corner of the craft, so the best "reading" here is a mix of a few durable references and the habit of checking current, authoritative sources before every real job. The resources below are grouped by purpose. Titles and standards are real; specific figures, pages, and current recommendations should always be confirmed at the source, because — as this whole chapter insists — the numbers move.

A note on tiers (see the book's citation policy): everything here is a Tier-1 genuinely-existing work, standard, or tool, or a Tier-2 attributed body of guidance. Where a resource updates constantly (a platform's help pages, a tool's manual), treat the current version as the authority and anything printed as a snapshot.

Foundational books (the durable context)

• Steven Ascher & Edward Pincus — The Filmmaker's Handbook. The standard one-volume reference for the whole production pipeline, with substantial, plain-language coverage of codecs, compression, formats, output, and delivery. If you own one book alongside this one, own this; its chapters on files, workflows, and finishing are the natural deepening of Chapters 3 and 36. (All paths; essential for pro-track and student.)
• Charles Poynton — Digital Video and HD: Algorithms and Interfaces. The deep, authoritative technical reference on how digital video actually works — sampling, gamma, color spaces, chroma subsampling, and encoding. This is advanced and math-forward; you do not need it to deliver correctly, but if you ever want to truly understand why 4:2:0 and Rec.709 behave as they do, this is the source the professionals cite. (Pro-track, and the curious 🔬 The Tech reader; skippable for everyone else.)
• Blain Brown — Cinematography: Theory and Practice. Primarily a shooting-and-lighting book, but its chapters on digital image, color, and the post pipeline connect the grade you finish (Chapters 31–32) to the file you deliver. Useful for seeing delivery as the end of a color chain, not an isolated step. (Creator, pro-track.)
• Walter Murch — In the Blink of an Eye. Not a delivery book at all — it is about editing and emotion — but it earns a place here for one reason: it is the clearest argument that the finished piece is a made object with intention in every frame, which is exactly the mindset that makes you refuse to click "Export" carelessly. Read it for why the last ninety minutes deserve the same care as the first ninety hours. (All paths; short and worth it.)

Standards worth knowing exist (you don't memorize these — you look them up)

• EBU R128 and ITU-R BS.1770 — loudness. The European broadcast loudness recommendation (R128, built on the BS.1770 measurement algorithm) is the reference behind "master to an integrated LUFS target with a true-peak ceiling." Knowing these exist tells you why broadcast runs near -23 LUFS and streaming near -14, and where to find exact figures when a spec demands them. (Pro-track; anyone delivering to broadcast.)
• ATSC A/85 — North American loudness. The U.S. counterpart standard (loudness measured in LKFS, practically the same unit as LUFS), the reason a North American broadcast deliverable targets around -24 LKFS. You will meet it the first time a U.S. broadcaster or network hands you a spec. (Pro-track.)
• ITU-R Rec.709 and Rec.2020 — color spaces. The delivery color standards for HD (709) and UHD/HDR-wide-gamut (2020). Your deliverables live in one of these; when a spec says "Rec.709," this is what it means. Introduced in Chapter 3 and applied in Chapters 31–32; here they are the color contract your export must honor. (Creator, pro-track.)
• W3C WCAG (Web Content Accessibility Guidelines). The widely referenced accessibility standard behind the delivery-time rules in §36.5 — caption requirements, the "no more than three flashes in one second" photosensitivity guideline, and contrast/legibility for on-screen text. You don't read it cover to cover; you know it's the authority when someone asks "is this accessible?" (All paths; essential for anyone delivering publicly or to institutions.)
• Caption file formats: SubRip (.srt) and WebVTT (.vtt). The two universal sidecar caption formats. .srt is dead simple (number, timecode range, text, blank line); .vtt is its web-oriented cousin with more styling. Knowing the format lets you write, fix, or convert captions by hand in any text editor. (Creator, phone-first, student.)

Free tools and apps (the ones you'll actually use)

• DaVinci Resolve (free) — the Deliver page and its manual. This book's reference editor handles the entire chapter for free: masters, platform deliverables, sidecar or burned-in captions, and a render queue for batching. Its official manual and training materials document every field in FIGURE 36.1 by name. The single best hands-on companion to this chapter. (All paths; Appendix E maps its buttons to other NLEs.)
• HandBrake (free, open-source). A dedicated transcoder for turning one file into another codec/size — perfect for making a small H.264 deliverable from your master when you want to hit a specific size with minimal damage, without re-opening your project. Learn it as your "make a clean smaller copy" tool. (Creator, pro-track.)
• FFmpeg (free, open-source). The command-line engine underneath a huge amount of video software. Overkill for most readers, but unbeaten for inspecting, re-wrapping (changing a container without re-encoding), and batch-converting files. Worth knowing it exists the day you need to re-wrap a hundred clips or fix a container problem. (Pro-track, the technical reader.)
• MediaInfo (free). A small utility that opens any video file and tells you exactly what's inside — codec, container, bitrate, bit depth, chroma, frame rate, audio format. This is how you answer Chapter 3's and this chapter's recurring question "what codec is actually in this box?" instead of guessing from the extension. (All paths; genuinely useful, install it.)
• A calibrated (or at least trusted) monitor, and a plain media player. Not an app to buy so much as a habit: QC your exports on a screen you trust and in a player that isn't your editor. VLC and the like play virtually anything and show you the file, not the timeline. (All paths.)

Platform and current-spec resources (the authorities that change)

• Each platform's own "recommended upload / encoding settings" help pages. YouTube, Instagram, TikTok, Vimeo, and the rest publish current recommended specs — resolution, codec, bitrate, aspect ratio, caption support. These are the real delivery specs, and they update without notice, which is why this chapter refuses to hardcode their numbers. Bookmark the ones you deliver to, and check them before a paid job. (All paths; non-negotiable for creators and pro-track.)
• Vimeo's compression/encoding guides. Vimeo has long published clear, creator-friendly explanations of export settings and why they matter — a good plain-language companion to §36.1–36.2 when a platform's own help feels terse. (Creator, phone-first.)
• Reputable creator-education channels on export and delivery. Several well-regarded editing and color channels publish careful, tool-specific walkthroughs of the Resolve Deliver page, codec choices, and caption workflows. Use them for how-to-click; use this chapter and the books above for why. Prefer sources that explain the reasoning and hedge on specs over ones that hand you a single "best export settings" preset as if it were permanent. (Creator, student.)
• A broadcaster's or platform's delivery specification document (when you get one). The most important "reading" for any pro delivery is the two-page spec the client or broadcaster hands you. Read it line by line, match every field, and ask about anything ambiguous. No general resource substitutes for the specific spec of the specific job. (Pro-track.)

A suggested order

1. Start with this chapter's own figures — the export dialog (36.1), the platform table (36.3), and the checklist (36.6) are your working reference. Screenshot the key-takeaways card.
2. Install MediaInfo and open a few files — make Chapter 3's box-vs-contents idea concrete before you read anything heavier.
3. Do the Deliver page in DaVinci Resolve with its manual open — export a master and one deliverable while reading §36.2–36.4. Learning-by-exporting beats learning-by-reading here.
4. Bookmark the current help pages for the two or three platforms you actually deliver to. Check them today; note the date.
5. Then, for depth: Ascher & Pincus for the pipeline context, and — only if you want the real physics — Poynton for how it all works underneath.

Which path each serves

• 📱 Phone-first: this chapter's figures, MediaInfo, .srt basics, and the platform help pages. Your app makes most codec choices; your job is highest-quality export, matched aspect, and burned-in captions.
• 🎥 Creator: Resolve's Deliver page, HandBrake, Vimeo's guides, the reputable creator channels, and the platform specs you upload to weekly. Master the master-and-deliverables discipline.
• 💼 Pro-track: all of it, plus the loudness standards (R128/A/85), Rec.709/2020, and — above all — the specific delivery spec document of every paid job. Ascher & Pincus and Poynton for depth.
• 🎓 Student: this chapter, Resolve + its manual, WCAG for accessibility, and Ascher & Pincus for the pipeline context that ties Chapters 3, 31–33, and 36 together.

Read a little, then export a lot. Delivery is learned at the render dialog, watching your own files on a phone and a big screen — which is exactly where Chapter 37 picks up, making sure the masters you just rendered are never lost.