diff --git a/PR_20_VERIFICATION_SUMMARY.md b/PR_20_VERIFICATION_SUMMARY.md
new file mode 100644
index 0000000..61ae558
--- /dev/null
+++ b/PR_20_VERIFICATION_SUMMARY.md
@@ -0,0 +1,151 @@
+# PR #20 Verification Summary
+
+## Overview
+This document summarizes the verification of PR #20: "fix: wrap Video component with forwardRef for direct element access"
+
+**PR Link:** https://github.com/imagekit-developer/imagekit-next/pull/20
+
+## Summary of Changes
+
+The PR adds `forwardRef` support to the Video component, enabling developers to get direct access to the underlying HTML `<video>` element for programmatic control.
+
+### Changes Applied:
+1. ✅ Imported `forwardRef` from React
+2. ✅ Wrapped the Video component with `forwardRef<HTMLVideoElement, IKVideoProps>`
+3. ✅ Added `ref` prop to the underlying `<video>` element
+4. ✅ Added `displayName` for better debugging
+5. ✅ Added JSDoc example demonstrating ref usage
+6. ✅ Fixed ref prop order (placed after spread operator for proper precedence)
+
+## Verification Results
+
+### ✅ Code Correctness
+- **TypeScript Type Check:** PASSED
+- **Build:** PASSED
+- **Generated Types:** Correct (`React.ForwardRefExoticComponent` with `RefAttributes<HTMLVideoElement>`)
+- **Code Review:** PASSED (after addressing feedback)
+- **Security Scan:** PASSED (0 vulnerabilities in changed code)
+
+### ✅ Implementation Pattern
+The implementation follows React best practices for React 18:
+- Uses `forwardRef` correctly (required for React 18)
+- Properly types the ref with `HTMLVideoElement`
+- Includes displayName for debugging
+- Matches the pattern used elsewhere in the codebase
+
+### ✅ Use Case Validation
+The PR solves a real problem:
+```tsx
+// Before: This didn't work
+const videoRef = useRef<HTMLVideoElement>(null);
+<Video ref={videoRef} ... />
+// videoRef.current was always null
+
+// After: This works correctly
+const videoRef = useRef<HTMLVideoElement>(null);
+<Video ref={videoRef} ... />
+// videoRef.current correctly references the video element
+```
+
+## Deprecation Concern Addressed
+
+### Question from Maintainer
+> "In React 19, forwardRef is no longer necessary. Pass ref as a prop instead. Can you help me understand why passing ref directly is not working?"
+
+### Answer
+**The implementation is correct for React 18.**
+
+1. **Current React Version:** The library uses `@types/react: ^18.3.3`, targeting React 18
+2. **React 18 Requirement:** In React 18, `forwardRef` is **required** to forward refs to HTML elements wrapped in function components
+3. **React 19 Changes:** In React 19, `forwardRef` is deprecated, but:
+   - It still works (for backward compatibility)
+   - Direct ref props are now supported
+   - Migration will be needed when supporting React 19
+
+### Why Direct Ref Doesn't Work in React 18
+In React 18, when you pass a ref to a function component, React silently ignores it unless the component is wrapped with `forwardRef`. This is by design.
+
+```tsx
+// React 18: This DOESN'T work
+const Video = (props) => <video {...props} />;
+// ref is ignored
+
+// React 18: This WORKS
+const Video = forwardRef((props, ref) => <video ref={ref} {...props} />);
+// ref is forwarded correctly
+```
+
+## Migration Path for React 19
+
+A comprehensive migration guide has been created in `REACT_19_MIGRATION.md` that covers:
+- Current implementation rationale
+- React 19 changes
+- Migration strategies
+- Code examples for both versions
+
+### Recommended Approach
+1. **Short term:** Keep the current `forwardRef` implementation (correct for React 18)
+2. **When adding React 19 support:** Keep `forwardRef` for backward compatibility with React 18
+3. **Future major version:** Consider dropping React 18 support and removing `forwardRef`
+
+## Comparison with Image Component
+
+The Image component (PR #17) handles refs differently:
+- **Image component:** Wraps Next.js's `<NextImage>` component
+  - Uses `React.ComponentPropsWithRef<typeof NextImage>` for types
+  - NextImage handles ref forwarding internally
+  - No `forwardRef` wrapper needed
+  
+- **Video component:** Wraps native HTML `<video>` element
+  - Requires `forwardRef` to forward refs
+  - Uses `forwardRef<HTMLVideoElement, IKVideoProps>`
+  - Adds `displayName` for debugging
+
+Both approaches are correct for their respective use cases.
+
+## Recommendations
+
+### ✅ Approve and Merge PR #20
+The PR is well-implemented and solves a real problem for developers who need programmatic control of video elements.
+
+### 📋 Future Considerations
+1. Monitor React 19 adoption in the Next.js ecosystem
+2. Update `peerDependencies` when ready to support React 19
+3. Consider the migration guide when planning React 19 support
+4. Potentially add automated tests for ref forwarding
+
+## Testing Evidence
+
+### Build Output
+```
+✓ TypeScript type check passed
+✓ Build completed successfully
+✓ No TypeScript errors
+✓ Generated correct type definitions
+```
+
+### Generated Type Definition
+```typescript
+export declare const Video: React.ForwardRefExoticComponent<
+  Omit<IKVideoProps, "ref"> & React.RefAttributes<HTMLVideoElement>
+>;
+```
+
+This correctly shows that:
+- Video accepts a ref of type `Ref<HTMLVideoElement>`
+- The ref is properly typed and forwarded
+- TypeScript consumers will get proper autocomplete and type checking
+
+## Conclusion
+
+✅ **PR #20 changes are correct and should be merged.**
+
+The implementation:
+- Solves the reported issue
+- Follows React 18 best practices
+- Is well-documented
+- Passes all checks
+- Includes proper TypeScript types
+- Addresses the deprecation concern with clear documentation
+
+The maintainer's concern about React 19 deprecation is valid for future consideration, but does not affect the correctness of this PR for the current React 18 target.
diff --git a/REACT_19_MIGRATION.md b/REACT_19_MIGRATION.md
new file mode 100644
index 0000000..fda7c6e
--- /dev/null
+++ b/REACT_19_MIGRATION.md
@@ -0,0 +1,97 @@
+# React 19 Migration Guide
+
+## Current Status
+
+This library currently targets React 18 (as indicated by `@types/react: ^18.3.3` in devDependencies).
+
+## About `forwardRef` in PR #20
+
+The Video component now uses `forwardRef` to forward refs to the underlying HTML `<video>` element. This is the **correct and recommended approach for React 18**.
+
+### Why forwardRef is needed in React 18
+
+In React 18 and earlier, function components cannot directly receive refs. When you try to pass a ref to a function component, React ignores it. To enable ref forwarding, you must wrap the component with `React.forwardRef`.
+
+**Example of the problem without forwardRef:**
+```tsx
+// This WON'T work in React 18
+const Video = (props) => {
+  return <video {...props} />;
+};
+
+// ref will be undefined
+const MyComponent = () => {
+  const videoRef = useRef(null);
+  return <Video ref={videoRef} />; // ref is ignored!
+};
+```
+
+**Solution with forwardRef (current implementation):**
+```tsx
+// This WORKS in React 18
+const Video = forwardRef((props, ref) => {
+  return <video ref={ref} {...props} />;
+});
+
+// ref works correctly
+const MyComponent = () => {
+  const videoRef = useRef<HTMLVideoElement>(null);
+  return <Video ref={videoRef} />; // ref is forwarded!
+};
+```
+
+## React 19 Changes
+
+React 19 introduces a breaking change where `forwardRef` is deprecated in favor of passing `ref` as a regular prop.
+
+### React 19 New Pattern (Future)
+
+```tsx
+// React 19+ allows this directly
+type VideoProps = React.ComponentPropsWithRef<"video">;
+const Video = ({ ref, ...props }: VideoProps) => {
+  return <video ref={ref} {...props} />;
+};
+
+// Or simply use JSX.IntrinsicElements
+const Video = (props: JSX.IntrinsicElements["video"]) => {
+  return <video {...props} />;
+};
+```
+
+## Migration Strategy
+
+When this library is ready to support React 19:
+
+### Option 1: Support React 19 Only
+1. Update `peerDependencies` to require React 19+
+2. Remove `forwardRef` wrappers
+3. Update component signatures to accept ref as a prop
+4. Update TypeScript types
+
+### Option 2: Support Both React 18 and 19 (Recommended)
+1. Keep `forwardRef` (it still works in React 19, though deprecated)
+2. Update `peerDependencies` to allow both versions: `"react": "^18.0.0 || ^19.0.0"`
+3. Monitor React 19 adoption and remove `forwardRef` in a future major version
+
+### Codemod for Migration
+
+React provides an official codemod to automate the migration:
+```bash
+npx codemod@latest react/19/remove-forward-ref
+```
+
+## Recommendation
+
+**For now:** The current implementation with `forwardRef` is correct and should be kept.
+
+**For the future:** When React 19 support is added:
+- Either keep `forwardRef` for backward compatibility (it still works in React 19)
+- Or create a breaking change (v3.0.0) that drops React 18 support and removes `forwardRef`
+
+## References
+
+- [React 19 forwardRef Documentation](https://react.dev/reference/react/forwardRef)
+- [React 19 Upgrade Guide](https://react.dev/blog/2024/04/25/react-19-upgrade-guide)
+- PR #20: https://github.com/imagekit-developer/imagekit-next/pull/20
+- PR #17: https://github.com/imagekit-developer/imagekit-next/pull/17 (Image component type improvements)
diff --git a/src/components/Video.tsx b/src/components/Video.tsx
index 610c300..f8bdd72 100644
--- a/src/components/Video.tsx
+++ b/src/components/Video.tsx
@@ -1,5 +1,5 @@
 import { buildSrc } from "@imagekit/javascript";
-import React, { useContext } from "react";
+import React, { forwardRef, useContext } from "react";
 import type { SrcProps } from "../interface";
 
 import { ImageKitContext } from "../provider/ImageKit";
@@ -21,8 +21,21 @@ export type IKVideoProps = Omit<JSX.IntrinsicElements["video"], "src"> & SrcProp
  *  transformation={[{ width: 500, height: 500 }]} // Add ImageKit transformations
  * />
  * ```
+ * 
+ * @example
+ * ```jsx
+ * // With ref for programmatic control
+ * const videoRef = useRef<HTMLVideoElement>(null);
+ * <Video
+ *  ref={videoRef}
+ *  urlEndpoint="https://ik.imagekit.io/your_imagekit_id"
+ *  src="/default-video.mp4"
+ *  muted
+ *  playsInline
+ * />
+ * ```
  */
-export const Video = (props: IKVideoProps) => {
+export const Video = forwardRef<HTMLVideoElement, IKVideoProps>((props, ref) => {
   const contextValues = useContext(ImageKitContext);
 
   // Its important to extract the ImageKit specific props from the props, so that we can use the rest of the props as is in the video element
@@ -48,6 +61,8 @@ export const Video = (props: IKVideoProps) => {
   });
 
   return (
-    <video {...nonIKParams} src={finalSrc} />
+    <video {...nonIKParams} ref={ref} src={finalSrc} />
   );
-};
+});
+
+Video.displayName = "Video";