---
title: "Discussion on \"Deep-Linking Into YouTube Videos: t=, start=, end= and the IFrame API Explained\" | Hashnode"
description: "Discussion on \"Deep-Linking Into YouTube Videos: t=, start=, end= and the IFrame API Explained\". If you build documentation sites, course platforms, changelogs, or internal wikis, sooner or later you want a link that drops the reader into a video at the exact second that matters. YouTube supports"
url: "https://hashnode.com/posts/deep-linking-into-youtube-videos-t-start-end-and-the-iframe-api-explained/6ae96e09e69abdf4cc19d855"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Deep-Linking Into YouTube Videos: t=, start=, end= and the IFrame API Explained](https://toolsphare-dev-2026.hashnode.dev/deep-linking-into-youtube-videos-t-start-end-and-the-iframe-api-explained?utm_source=hashnode&utm_medium=feed)

If you build documentation sites, course platforms, changelogs, or internal wikis, sooner or later you want a link that drops the reader into a video at the exact second that matters. YouTube supports

Nov 3 · 6 min read · toolsphare-dev-2026.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#youtube](https://hashnode.com/tag/youtube)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#api](https://hashnode.com/tag/api)
-   [#frontend](https://hashnode.com/tag/frontend)

## Written by

[Muhammad Wasim](https://hashnode.com/@toolsphare)

@toolsphare

  
[View profile](https://hashnode.com/@toolsphare)

Founder of ToolSphare; privacy-minded free developer and productivity utilities.

I build ToolSphare, a privacy-minded collection of free browser utilities for developers and everyday workflows.

## Responses 1

Markdown supported · ⌘↵ to post

[DemoVexa](https://hashnode.com/@demovexa)

[4d ago](https://hashnode.com/posts/deep-linking-into-youtube-videos-t-start-end-and-the-iframe-api-explained/6ae96e09e69abdf4cc19d855/comment/6af135d74c646a52bf80fd18)

The t= versus start= trap explains a lot of "timestamped" links that quietly begin at zero, especially when someone pastes a watch link into an iframe src. Converting every input to integer seconds first is the cleanest way to stop that. For changelogs and docs I'd add one habit: store the video ID and the start and end seconds as data, and build the URL when the page renders. When a video gets replaced, you update one record instead of hunting through pages for old links. Your chapters point fits that too. If the same three sections keep getting linked from the docs, chapters make them findable for viewers who arrive on YouTube and never see your site.