Embedding QuickTime Movies on Your Site
When a visitor lands on a page and a movie starts right in the middle of the content, the most common technique behind that experience is the QuickTime <object> and <embed> approach. Although browsers have evolved to support the <video> element, many legacy sites still rely on QuickTime for its proven compatibility with both Windows and macOS. The key to a smooth playback experience is to provide the browser with all the information it needs to download or invoke the QuickTime plug‑in, specify the video source, and present a consistent player interface.
The standard, minimal markup looks like this:
Notice how the <object> tag uses classid and codebase to point the browser to the ActiveX installer on Windows, while the <embed> tag supplies the pluginspage URL for macOS users who need to download QuickTime. The dimensions are set to 320×240 for the video content itself, and the height is increased by 16 pixels (256) to accommodate the controller strip. The controller and autoplay parameters give the site owner fine‑grained control over how the player behaves.
Using both tags ensures maximum compatibility. If a browser ignores <object>, it will still read <embed>, and vice versa. Once the plug‑in is in place, the browser streams the movie data directly into the player. If a user doesn’t have QuickTime installed, the plug‑in is prompted for installation automatically; if that fails, the user is redirected to Apple’s download page.
A frequent question is whether it’s acceptable to just link to the movie file instead of embedding it. That’s a valid alternative, especially for sites that want to keep the HTML lightweight. A simple link looks like this:
When the link is clicked, the browser opens the file with the default media player configured on the user’s machine. To aid decision‑making, it’s wise to display the file size next to the link, for example: Download (2.5 MB). This transparency helps visitors decide whether they’re ready to download large video files over slow connections.
Because the QuickTime format is still supported by many browsers, you can choose the file type that best suits your audience. A .mov file offers excellent compression and cross‑platform compatibility. If you need something lighter for bandwidth‑constrained environments, consider exporting to MPEG‑4 (.mp4) or H.264. Both of these formats are widely supported in modern browsers without a plug‑in, but using the QuickTime tags still works as a fallback on older systems.
In addition to the parameters shown above, you can control the player’s look‑and‑feel. Setting controller="true" exposes the play/pause slider and time display. If you prefer a cleaner look, set it to false and rely on JavaScript controls instead. The autoplay attribute dictates whether the video starts automatically or waits for the user’s click. For most sites, manual start is recommended to avoid disrupting the user’s browsing flow.
To fine‑tune the player further, Apple’s official QuickTime embedding guide offers a full list of supported parameters: http://www.apple.com/quicktime/authoring/embed.html. That resource covers everything from setting loop behavior to customizing the playback controls.
By combining <object> and <embed>, specifying source, dimensions, and controls, and adding a straightforward download link as a backup, you create a robust video presentation that works across the major desktop browsers of today.
Optimizing Video for Fast Loading
Once you’ve embedded a video, the next challenge is making it load quickly enough for users on all connection speeds. Video files can be several megabytes in size, which can frustrate visitors on dial‑up or mobile networks. Optimization is a multi‑step process that involves choosing the right file format, setting an appropriate resolution, controlling frame rate, adjusting color depth, and selecting the best codec for the target audience.
File format is the first decision. QuickTime’s .mov is a natural fit for sites that still use the QuickTime player, but modern browsers support .mp4 with H.264 encoding almost everywhere. H.264 delivers high quality at lower bitrates, making it ideal for streaming over broadband or even 3G networks. If you need the widest possible reach - including older Windows machines - use MPEG‑4 or even the older .avi format, but keep in mind that these may require additional plugins.
Resolution determines how much visual detail the user sees. Web‑friendly dimensions usually fall between 160×120 and 240×180 pixels for small inline videos, while larger background or feature videos can comfortably occupy 320×240 or 640×480. Anything larger than 320×240 is rarely necessary for most page layouts and can dramatically increase file size. When in doubt, test both a low‑resolution preview and the final high‑resolution version to gauge performance.
Frame rate is another lever. Standard video runs at 30 frames per second (fps), but that level of motion smoothness is often overkill for web playback. Reducing the frame rate to 15 or even 10 fps can cut file size by almost half without compromising the user’s perception of motion, especially for documentary or instructional content. Fast‑action movies may still benefit from 24 or 30 fps to maintain fluidity.
Color depth controls how many colors are represented in each pixel. A 24‑bit color depth (true color) produces the richest image but requires more data. If the visual content allows, lowering the depth to 8 bits reduces the bitrate while still delivering acceptable quality. This change is most effective when combined with a codec that performs well at lower color depths.
Bitrate, expressed in kilobits per second (Kbps), is arguably the most critical variable. A bitrate of 4 Kbps will stream comfortably over 56‑kbit dial‑up, 30 Kbps over DSL, and 50 Kbps over cable. Modern broadband users can handle higher rates - 200 Kbps or more - without buffering. When exporting from your editing software, look for “web” presets that automatically set these bitrate targets based on the selected connection type. If no preset exists, manually adjust the bitrate slider while monitoring the estimated file size.
Codec choice affects both quality and compatibility. H.263 and Sorenson Video provide excellent compression, but Sorenson requires a more powerful processor for playback, which may be a concern on older machines. Cinepak offers broader compatibility and decodes quickly, making it a safe fallback for users with limited hardware. If your audience includes a mix of high‑end and low‑end devices, consider offering multiple versions of the same video and using a simple JavaScript selector to pick the best match.
Once you’ve set these parameters, export the video and run it through a quick test on the target browsers. Use a tool like
No comments yet. Be the first to comment!