# Embedding pens from CodePen

**URL:** https://meta.discourse.org/t/embedding-pens-from-codepen/13578
**Category:** Feature
**Created:** [March 9, 2014, 9:56pm UTC](https://meta.discourse.org/t/embedding-pens-from-codepen/13578 "2014-03-09T21:56:57Z")
**Posts on this page:** 1
**Showing post:** 31

<div class="post-metadata">

### Author: ![chriscoyier](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chriscoyier/32/108376_2.png) [@chriscoyier](https://meta.discourse.org/u/chriscoyier)
#### Post date: [October 15, 2015, 8:57pm UTC](https://meta.discourse.org/t/embedding-pens-from-codepen/13578/31 "2015-10-15T20:57:09Z")

</div>

Hey Team!

We’ve worked on a fix for this: **click-to-play** , as you suggested.

We haven’t deployed it yet, but it would be how all oEmbed embedded Pens would behave.

1. When the embed loads, you get a (very lightweight) placeholder with the title of the Pen and author and such. Plus a big “Run Pen” button.

2. If anywhere on there is clicked/tapped, it loads the embed.

Thus, no unexpected sound, no unexpected crazy CPU use, no going to a page with a zillion embeds and feeling the lag, etc.

 ![](https://global.discourse-cdn.com/meta/original/3X/2/3/238ad75d12ab58a95fb6130bfa7fa5d1954e1a1c.gif)

That work for you?

---

_[View the full topic](https://meta.discourse.org/t/embedding-pens-from-codepen/13578)._