Pinecast changelog Pinecast changelog https://changelog.pinecast.com WordPress Sync Plugin v2.3.0 Matt Tue, 03 Nov 2026 18:36:36 -0000 https://changelog.pinecast.com/wordpress-sync-plugin-v2-3-0 wordpress-sync-plugin-v2-3-0 <p>Version 2.3.0 of our WordPress Sync plugin. You can upgrade in your WordPress admin dashboard.</p> <p>This release includes a number of fixes:</p> <ul> <li>When your feed can&#39;t be refreshed, you&#39;ll see an error and the &quot;last updated&quot; time won&#39;t change.</li> <li>New versions of PHP no longer show a deprecation warning.</li> <li>Hosts that lack the <code>fileinfo</code> extension will no longer cause a sync to crash when loading artwork.</li> <li>Invalid categories and tags are no longer saved when no categories or tags are selected.</li> </ul> <p>There are some new features as well:</p> <ul> <li>Timecodes in your show notes link the player to that time.</li> <li>The UI of the Pinecast settings page is now cleaner and follows the design patterns of WordPress more closely.</li> <li>Posts now display episode chapters.</li> </ul> New Podcast Chapters and M4A support Matt Tue, 03 Nov 2026 17:20:30 -0000 https://changelog.pinecast.com/podcast-chapters podcast-chapters <p>We&#39;ve just launched one of the biggest updates to the Pinecast in a while. This new update has a lot in it, and it should make your experience with Pinecast a bit better.</p> <h1>Podcast chapters</h1> <p>We now fully support podcast chapters. If you upload an audio file with chapters in the metadata, we&#39;ll read them out and apply them to your episode. You can edit them in the brand new &quot;Chapters and clip placeholders&quot; editor:</p> <p><img src="https://changelog.pinecast.com/changelog-images/podcast-chapters/editor.png" alt="Podcast chapter and clip placeholder editor"></p> <p>This UI replaces the existing clip placeholders field. We now show a GUI that allows you to seek through your episode to add clip placeholders and chapters on the waveform timeline. Chapters that were in your audio&#39;s metadata are pre-loaded into the editor.</p> <h2>Getting chapters</h2> <p>We make chapters available across your podcast:</p> <ul> <li>Your RSS and JSON feeds will link to a Podcasting 2.0-compatible chapter manifest. This is read by apps like Apple Podcasts.</li> <li>You can include chapters automatically in your show notes. Under your podcast <strong>Settings</strong> tab, visit the <strong>Episode formatting</strong> view. By default, chapters are not added to show notes. You can add them to the end or the beginning of your show notes.</li> <li>There&#39;s a new chapters page element available for podcast websites. All of our presets include the ability to show podcast chapters when someone visits the page for an episode.</li> <li>We write chapters into your audio file metadata, so even folks who download the audio file will see them.</li> <li>Update your WordPress Sync plugin to 2.3.0 to pull chapters in to your WordPress website.</li> </ul> <p>More chapters integrations are coming soon.</p> <h1>M4A support</h1> <p>Historically, we&#39;ve supported reading and writing metadata for MP3 files (via ID3 tags). Now, we also support the same features for M4A. We&#39;ll include:</p> <ul> <li>Episode metadata (title, podcast name, etc.)</li> <li>Episode artwork, if set</li> <li>Chapters (as <code>chpl</code> tags)</li> </ul> <p>If you already use AAC or M4A audio files, you don&#39;t need to change your workflow: keep using Pinecast as you always have and your files will benefit immediately.</p> <p>As always, we do not re-encode your audio files.</p> <h1>Drafts</h1> <p>Episode drafts now store your clip placeholders and chapters. Previously, clip placeholders were not saved in drafts.</p> New Text-to-speech warnings Matt Tue, 03 Nov 2026 17:16:58 -0000 https://changelog.pinecast.com/text-to-speech-warnings text-to-speech-warnings <p>It&#39;s our policy that audio uploaded to Pinecast is not fully text-to-speech or otherwise AI-generated. Content that you publish must include some non-generated content.</p> <p>Now, when you upload a file that appears to be fully generated, we&#39;ll warn you on the New Episode page that the file might violate our terms of use.</p> <p>Uploading content that violates our terms of use on our free demo plan will result in an automatic account suspension. On a paid plan, your account may be flagged for a review by our team.</p> New Export from Descript to Pinecast Matt Tue, 27 Oct 2026 18:24:44 -0000 https://changelog.pinecast.com/export-from-descript-to-pinecast export-from-descript-to-pinecast <p>If you&#39;re a Descript user, you can now export audio directly from Descript to Pinecast. You can read Descript&#39;s documentation on how to do this here:</p> <p><a href="https://help.descript.com/export-and-share/pinecast">https://help.descript.com/export-and-share/pinecast</a></p> <p>When you export from Descript to Pinecast, we&#39;ll ask you which podcast you&#39;d like to post the episode to. When you&#39;ve confirmed the podcast, we&#39;ll pull the episode and its transcript from Descript.</p> <p>Rather than publishing directly, we create an episode draft with the details from Descript and load up the New Episode page with that draft pre-loaded. You can publish it immediately or save the changes to publish at a later date.</p> <h1>Integrations</h1> <p>If you have a product that exports audio for podcasts and would like to integrate with Pinecast like this, please get in touch! We&#39;d love to hear from you.</p> New Generative cover art Matt Sat, 24 Oct 2026 13:32:28 -0000 https://changelog.pinecast.com/generative-cover-art generative-cover-art <p>All podcasts require cover art to be valid: this is a requirement from podcast apps and directories. However, this can be an outsized ask for some folks, especially those who have limited vision. Over the years, our support system has received over a dozen requests to create artwork by users who aren&#39;t able to easily do it themselves. This is a real problem, and a significant hurdle for folks with certain accessibility needs to start a podcast.</p> <p>Generative AI offers an incredible tool for folks who aren&#39;t able to easily create their own cover art. On the New Podcast and Podcast Settings pages, we now allow paid customers to generate artwork using Black Forest Labs&#39; FLUX.2 model. You can generate up to ten images every hour.</p> <p><img src="https://changelog.pinecast.com/changelog-images/generative-artwork/field.png" alt="The Cover Art field showing an option to generate cover art using AI"></p> <p>You&#39;ll first be presented with information about how the feature works, including details about what information is sent to our AI provider and how this affects you. On the second step, you can provide a description of what you&#39;d like the artwork to look like.</p> <p><img src="https://changelog.pinecast.com/changelog-images/generative-artwork/step2.png" alt="The Cover Art field showing an option to generate cover art using AI"></p> <p>We&#39;ll then generate the image, which can take up to a minute. When the image is returned, we&#39;ll show it along with a text description.</p> <p><img src="https://changelog.pinecast.com/changelog-images/generative-artwork/step3.png" alt="The Cover Art field showing an option to generate cover art using AI"></p> <h1>Our use of AI</h1> <p>In building this feature, we evaluated many image models, and settled on FLUX.2 for a few reasons:</p> <ol> <li>The model made very few mistakes when generating text</li> <li>The model avoids making artwork that would be outright rejected by most podcast apps and directories</li> <li>In our tests, the generated images were the most aesthetically interesting</li> </ol> <p>The text descriptions are created using Gemma 4. Gemma does a great job of describing the image subjectively, while also reading back the text exactly (including typos, which is important for folks who can&#39;t see issues in the image).</p> <p>Both models are open-weight, and run in an environment where no data is retained or repurposed for any reason. Only the information strictly required to complete the request is sent. As always, we do our best to use AI as responsibly as possible. You can always read about how Pinecast uses AI on our <a href="https://www.pinecast.com/ai-use">AI use page</a>.</p> New New themes Matt Wed, 21 Oct 2026 16:23:43 -0000 https://changelog.pinecast.com/new-themes new-themes <p>Starting today, there are four new podcast website theme presets available in the site builder. We&#39;ve been spending a lot of time improving the site builder and the tools behind the scenes that make podcast websites possible. Through that effort, we&#39;ve been able to craft four beautiful new themes that have striking colors and typography.</p> <p>Check them out in the site builder today:</p> <ul> <li>Broadsheet</li> <li>Nightcap</li> <li>Sunday</li> <li>Signal</li> </ul> <p>As usual, all of our themes use accessible defaults, are fully SEO-optimized, and built to load as quickly as possible.</p> New Analytics privacy Matt Wed, 21 Oct 2026 16:19:01 -0000 https://changelog.pinecast.com/analytics-privacy analytics-privacy <p>Pinecast allows you to configure an analytics provider to send analytics data to. We support many providers, including Dynamo, Podcorn, and more. These providers work by adding a &quot;prefix&quot; to the URLs of your episode audio. When a listener requests the audio, they access the provider before accessing Pinecast. This allows the provider to track the listen.</p> <p>This behavior, though, gives the analytics provider access to more than just details about the listener. If someone is a subscriber through your Tip Jar, the analytics provider also gets access to information about the private feed that your listener accesses Pinecast through. That feed includes information about episodes that are not public.</p> <p>While we recommend only using services that you trust, you can now disable forwarding analytics data to providers from paid Tip Jar feeds. This ensures that the provider doesn&#39;t get access to content that is otherwise non-public. Keep in mind that protecting your show in this way effectively disables the analytics provider for listeners who have a paid subscription.</p> New Podscribe Matt Wed, 21 Oct 2026 16:17:20 -0000 https://changelog.pinecast.com/podscribe podscribe <p>The Analytics settings tab on your podcast dashboard now allows you to forward your analytics data to Podscribe.</p> New Easier artwork and metadata Matt Wed, 21 Oct 2026 15:57:13 -0000 https://changelog.pinecast.com/easier-artwork-and-metadata easier-artwork-and-metadata <p>One of the most persistent issues on a major Pinecast page has been the artwork and metadata question that&#39;s posed when you upload your audio. First, some important context.</p> <h1>Why artwork and metadata is hard</h1> <p>The information that you upload to Pinecast is what goes into your RSS feed. This is available to podcast apps that pull your feed, but anyone downloading the episode audio as a file will lose the title, podcast name, and artwork.</p> <p>Additionally, some podcast apps do not use the artwork as it&#39;s listed in your RSS feed. Instead, they pull the artwork as an image file from inside the audio file&#39;s metadata (e.g., ID3 tags). If the artwork is not correctly added to the metadata, some listeners simply won&#39;t see it.</p> <h1>What we&#39;ve done in the past</h1> <p>In the past, when you chose an audio file, we&#39;d inspect it to ensure it contained artwork and metadata. If it did not, we&#39;d prompt you to add those items. When you added artwork or metaata, we&#39;d change the audio file to include them before we uploaded the file to our servers.</p> <p>This created a dependency: you can&#39;t save the episode until the audio is uploaded. The audio can&#39;t be uploaded until artwork and metadata are added. And we can&#39;t add the artwork and metadata if they haven&#39;t been given to us yet. For some folks, this was confusing. For others, it was annoying.</p> <h1>What we&#39;re doing now</h1> <p>You&#39;ll now see episode audio as a field just like you previously did. You&#39;ll also see two new fields:</p> <ol> <li><strong>A switch to add metadata to your episode.</strong> When selected, we&#39;ll automatically add metadata. We recommend leaving this enabled unless you&#39;re setting your own metadata.</li> <li><strong>An episode artwork upload field.</strong> You can add episode artwork or leave it empty: the field is optional.</li> </ol> <p>What&#39;s different is that we&#39;ll handle the processing on our end: we&#39;ll ensure the artwork and metadata are added <em>after</em> the file has been uploaded and saved. This means you&#39;re not nagged during the upload process. Skipping a step by accident doesn&#39;t require you to scroll back up.</p> <h2>Editing, too</h2> <p>One consequence of our old setup was that artwork and metadata were added <em>only at the point that audio was uploaded</em>. If you wanted to change your artwork, it required you to re-upload the audio file. Similarly, changing details like the name of your episode wouldn&#39;t be saved to the metadata.</p> <p>With the new setup, this all &quot;just works&quot;. You never need to re-upload audio to change artwork or metadata, and the Edit Episode UI should behave exactly as you expect it to.</p> Improvement Dark mode on login pages Matt Sat, 10 Oct 2026 17:44:50 -0000 https://changelog.pinecast.com/dark-mode-on-login-pages dark-mode-on-login-pages <p>On pages where you&#39;re signed out, like the login or signup pages, we now support dark mode. This also applies to the tip jar, so your listeners will also get to enjoy dark mode.</p> <p>Note: the appearance is based on the setting your browser informs us of. If you&#39;ve saved a custom dark mode preference (other than &quot;auto&quot;) in your Pinecast settings, your override won&#39;t apply until after you&#39;ve signed in.</p> Improvement Schedule posts for time Matt Wed, 07 Oct 2026 16:21:54 -0000 https://changelog.pinecast.com/schedule-posts-for-time schedule-posts-for-time <p>Under Settings &gt; Episode Formatting in your podcast dashboard, there&#39;s a new setting at the bottom of the page. </p> <p><img src="https://changelog.pinecast.com/changelog-images/schedule-posts-for-time/setting.png" alt="The new &quot;Default publish time&quot; setting on the Episode Formatting settings tab"></p> <p>This setting changes the default publish time on the New Episode page. For instance, set it to 4:00pm New York time, and your episodes will always default to 4:00pm New York time.</p> <h1>Time zone aware</h1> <p>If your episodes are set to 4:00pm New York time and you travel to Chicago, visiting the New Episode page will show 3:00pm—the page is smart enough to know that you&#39;re in a different time zone, and keep the publish time matching your preference.</p> <h1>Daylight savings aware</h1> <p>Publish times don&#39;t change when daylight savings changes. Set your episode to publish at 4:00 New York time, and you&#39;ll never be surprised at 3:00pm or 5:00pm when the seasons change. Your publish time will always default to 4:00pm.</p> New New analytics time ranges Matt Wed, 07 Oct 2026 16:17:59 -0000 https://changelog.pinecast.com/new-analytics-time-ranges new-analytics-time-ranges <p>The analytics in your dashboard got two new time ranges: &quot;Last month&quot; and &quot;This month so far&quot;.</p> <h1>Last month</h1> <p>&quot;Last month (month name)&quot; differs from &quot;Previous month&quot; in that &quot;Previous month&quot; shows the last thirty days, whereas &quot;Last month (month name)&quot; shows the full previous month. Today is October 7, so &quot;Last month (September)&quot; would show the full analytics for September (rather than September 7 through today).</p> <h1>This month so far</h1> <p>&quot;This month so far&quot; does exactly what it says on the tin. Today (October 7), selecting this option would show October 1 through the present moment.</p> New Importing transcripts Matt Mon, 05 Oct 2026 16:31:41 -0000 https://changelog.pinecast.com/importing-transcripts importing-transcripts <p>When importing your podcast from another host, we&#39;ll now bring along your existing transcripts, so long as they use the appropriate <code>&lt;podcast:transcript&gt;</code> tags. We&#39;ll do our best to choose which transcript format works best with Pinecast (if there&#39;s more than one), and convert it if necessary.</p> <p>We support importing transcripts in the following formats:</p> <ol> <li>VTT</li> <li>SRT</li> <li>SBV</li> <li>HTML (in the format specified by the Podcasting 2.0 standard)</li> <li>JSON (in the format specified by the Podcasting 2.0 standard)</li> </ol> <p>One important note: we don&#39;t store transcripts as raw text, we keep them in a format that lets us use them for other purposes. If the data we pull in for a transcript isn&#39;t valid (for instance, the transcript includes implausible timestamps that move backward through time), we won&#39;t be able to perform the import.</p> New Adding a transcript to new episodes Matt Thu, 01 Oct 2026 22:32:01 -0000 https://changelog.pinecast.com/adding-a-transcript-to-new-episodes adding-a-transcript-to-new-episodes <p>When creating an episode previously, the only transcription option was to have the episode transcribed. Now, you can choose to upload a VTT, SRT, or SBV file directly on the New Episode page.</p> <p><img src="https://changelog.pinecast.com/changelog-images/adding-a-transcript-to-new-episodes/upload-transcript.png" alt="A preview of the option to add a transcript"></p> New Subscriptions no longer cancel immediately Matt Thu, 01 Oct 2026 22:30:34 -0000 https://changelog.pinecast.com/subscriptions-no-longer-cancel-immediately subscriptions-no-longer-cancel-immediately <p>When you cancel your Pinecast subscription, it now stays active until the end of the payment period. If you decide to re-enable your subscription before the end of your payment period, that option is now available to you, and you&#39;ll continue to be billed.</p> Change October 2026 Accessibility Update Matt Thu, 01 Oct 2026 21:41:29 -0000 https://changelog.pinecast.com/october-2026-accessibility-update october-2026-accessibility-update <p>Hey Pinecasters, I&#39;m super excited to announce the release of our October 2026 accessibility update. We&#39;re getting ready to make some noise about our committment to accessibility at Pinecast, and part of that is understanding how well we are doing. While preparing the report, we made a choice: every accessibility finding (that is, every issue that could affect how well a user interacts with our software) either needs to be a deliberate choice made for a good reason, or it&#39;s a bug.</p> <p>We spent the last two weeks combing through hundreds of thousands of lines of code. We found 200 problems. 11 were for features that are currently under construction or not yet live, 18 were flagged as deliberate choices, and one is pending additional changes. 170 problems were fixed.</p> <p>I don&#39;t want to get into the nitty gritty of all of the individual changes that were made, but we took a lot of time to get things polished, and I want to highlight some of what shipped.</p> <h1>For folks who don&#39;t use a pointing device</h1> <p>Everything that works with a mouse should work with a keyboard.</p> <ul> <li>We fixed numerous issues that prevented you from tabbing through the UI in a sensible way. In thirteen places, we fixed the browser focus jumping back to the top of the page: to all the folks that have been bitten by issues like this, we&#39;re terribly sorry for the frustration.</li> <li>Ten types of controls were hard or impossible to use without a mouse. It&#39;s now easier to use the site builder, analytics, audio players, and our pricing pages.</li> <li>Eleven different parts of pinecast.com didn&#39;t make it clear what was selected as you tabbed through the page. We now rigorously test that each and every control that can be focused shows that it&#39;s focused.</li> </ul> <h1>For folks who use a screen reader</h1> <p>While good, we often didn&#39;t go far enough to help screen readers understand exactly what users were interacting with. Almost seventy different parts of Pinecast were updated to make screen reader support world-class.</p> <ul> <li>Everything that you can interact with—from buttons to text boxes to sliders—all now carry information needed for screen readers to understand them correctly. That accounted for 33 of the problems fixed.</li> <li>It&#39;s now easier to access our support chat, which had been hidden in some cases.</li> <li>The old, awful calendar control is gone. We&#39;re so sorry it took so long to replace this.</li> <li>Titles, headings, and landmarks on the page are now correctly structured and ordered. It should be a lot easier to get around.</li> <li>When something happens, it&#39;ll be announced—be it a save, edit, or delete.</li> </ul> <h1>For folks with low vision or color blindness</h1> <p>We looked at colors, sizes, and how browsers zoom in.</p> <ul> <li>Everything is much higher-contrast. We&#39;ve made a ton of changes around how controls like buttons, charts, and focus outlines around the site look.</li> <li>The site builder has better color pallettes that meet minimum contrast requirements. If you use a podcast website preset that you haven&#39;t customized, your site automatically picks up the color changes.</li> <li>For places where color differentiates different kinds of information, we now use other details like different shapes or textures.</li> <li>If you zoom in or use a large text setting on your device, our pages look better and avoid requiring you to scroll horizontally.</li> </ul> <h1>For folks with sensitivity to motion or need a little extra time</h1> <p>We fixed twelve problems across our properties.</p> <ul> <li>&quot;Reduce motion&quot; settings now affect 100% of Pinecast—no unexpected transitions or animations.</li> <li>Notifications don&#39;t disappear on their own: you won&#39;t see things disappear as soon as your eyes land on them.</li> <li>Tooltips now work for folks who only use a keyboard as well. No hidden information.</li> </ul> <h1>For folks who are deaf and hard of hearing</h1> <p>Podcasting is an audio medium, but we&#39;ve invested and continue to invest in transcripts.</p> <ul> <li>Transcripts are now on by default. You can opt in or out of transcripts on a per-episode basis.</li> <li>All web players now link to transcripts when they&#39;re available. This comes in addition to captioning support, which already existed.</li> <li>The podcast playlist player now shows captions in full.</li> </ul> <h1>The curb-cut effect</h1> <p>The best part of accessibility support is that <a href="https://en.wikipedia.org/wiki/Curb_cut_effect">everyone benefits</a>, not just the folks that the improvements were designed to help.</p> <ul> <li>Any difficult-to-reverse decision (deletions, subscription changes, etc.) now have a confirmation step.</li> <li>Lots of places where errors happened without much explanation now do a much better job of explaining what went wrong. Fixing the error for low-vision users made the errors better for all users.</li> <li>Semantic changes to podcast websites better follow web best practices, which can make it easier for search engines and other crawlers to index your content.</li> </ul> <h1>For your listeners, too</h1> <p>These improvements aren&#39;t just on the pages you as a podcaster see. We&#39;ve fixed the pages your listeners see as well.</p> <ul> <li>Our site builder now recommends improved colors when you choose custom options that aren&#39;t high enough contrast to meet web accessibility guidelines. We do our best to suggest not just a good color, but tell you <em>which</em> color setting is the best one to change.</li> <li>Podcast websites saw improvements to the markup, making them friendlier to screen readers and folks who use features like &quot;Reader mode&quot;.</li> <li>Embeddable players and subscription links have better descriptions on controls, have better contrast, and work better with the keyboard.</li> <li>Show notes keep their formatting and language, making them read better with a screen reader.</li> </ul> <h1>Not just a one-off release</h1> <p>We wrote tests that check the accessibility of <em>every page</em> on Pinecast. If something changes that affects accessibility, we have an exhaustive suite that will flag the problem and require changes before it can be shipped to you. Across all of our properties, we&#39;ve added almost 40K lines of code to test for accessibility, covering things like the contrast of the color pallettes we use in light and dark mode, the colors we offer in the site builder, that every control has focus rings for folks using their keyboard to tab through the UI, and more.</p> <h1>What&#39;s next</h1> <ol> <li>More automated testing is on the way: our improvements aren&#39;t worth it if we don&#39;t stay ahead of the curve when it comes to accessibility.</li> <li>The tip jar is going to see a big UI update soon, and we&#39;re excited to help ensure your listeners who require accommodations have a great experience while using it.</li> <li>We&#39;ll be publishing a formal report with the full details of accessibility at Pinecast.</li> </ol> Improvement Transcription enabled by default Matt Fri, 25 Sep 2026 19:27:37 -0000 https://changelog.pinecast.com/automatic-transcription-enabled-by-default automatic-transcription-enabled-by-default <p>Starting soon, new podcasts will have automatic transcription enabled by default. We now allow you to choose on an episode-by-episode basis whether to transcribe the audio, so no transcription is performed without any visual consent. Automatic transcription can still be disabled in your podcast settings.</p> Change Analytics audit update Matt Sat, 19 Sep 2026 17:43:59 -0000 https://changelog.pinecast.com/analytics-audit-update analytics-audit-update <p>Periodically, we perform an audit of our analytics data to ensure we&#39;re doing the best job we possibly can to keep your analytics free from junk/bot listens. With the rise of AI, this work has gotten increasingly difficult, as it&#39;s become easier and easier for bad actors to download episodes covertly.</p> <p>We don&#39;t normally announce analytics audits, but this one is notable because it includes the most substantial changes we&#39;ve had in a long time.</p> <ol> <li>First, we&#39;ve dramatically expanded our corpus of data used to determine whether a listen came from a legitimate listener device or from a bot running in a data center. We&#39;ve more than 10x-ed the number of rules that we run against each and every listen.</li> <li>We&#39;ve worked to classify even more podcatchers and browsers, including ones that are not well known. For podcasters, this means you&#39;ll see more names appear under your &quot;Listens by agent&quot; view.</li> <li>We&#39;ve combed through our old rules and weeded out ones that aren&#39;t useful anymore. This is important, because some old rules are doing more harm than good. For example, apps claiming to be Google Podcasts are definitely illegitimate: Google Podcasts was rolled up into YouTube Music quite a while ago.</li> <li>Many of our existing rules were refined, helping to mark somewhat-suspicious listens from obscure devices as definitely legitimate or spammy.</li> </ol> <h1>Process change</h1> <p>Historically, for big updates like this, we&#39;d re-process existing analytics data. While this has been our policy (it gives you the <em>most accurate</em> information possible), it would be very disruptive for us to do this to all Pinecast customers today given the substantial amount of bot traffic we&#39;re seeing this year. Starting today, we&#39;re changing that policy. If you&#39;d like your analytics data filtered using the new rules, we&#39;re happy to do so upon request. Please reach out to Pinecast support through the chat in your dashboard or at <code>support@pinecast.com</code> and we&#39;ll be glad to assist you.</p> Improvement Site Builder 2.0 Matt Wed, 02 Sep 2026 11:42:00 -0000 https://changelog.pinecast.com/site-builder-overhaul site-builder-overhaul <p>We&#39;ve redesigned the Pinecast site builder to be cleaner and easier to understand.</p> <p><img src="https://changelog.pinecast.com/changelog-images/site-builder-overhaul/preview.png" alt="A preview of the overhauled site builder"></p> <p>The site builder is one of the most feature-rich parts of Pinecast, but its sheer size and complexity has made it hard for many folks to fully take advantage of. This month, we took a pass at cleaning up the design and making the UI more intuitive.</p> <p>First, there&#39;s no longer multiple layers of tabs and dropdowns: there&#39;s one clean sidebar. Click into a section and drill down to find what you need. The back button at the top returns you to the preview section instead of immediately leaving.</p> <p>Next, the Layout tab: </p> <p><img src="https://changelog.pinecast.com/changelog-images/site-builder-overhaul/layout.png" alt="A preview of the new Layout tab"></p> <p>Before, the Layout tab grouped related parts of the site design together: header and footer, homepage and episode lists, episode pages, etc. This makes sense logically, but making simple changes to what you can see in the preview area required you to navigate between tabs and sub-tabs.</p> <p>Click between pages in the preview, and the Layout tab will follow you, updating to show what&#39;s on that page.</p> <p><img src="https://changelog.pinecast.com/changelog-images/site-builder-overhaul/highlight.png" alt="Hovering a layout module highlights it in the preview"></p> <p>Now, the Layout tab shows <em>all</em> of the parts of the page you can currently see, top to bottom. Not sure what you&#39;re looking at? Hover over a module in the sidebar and it&#39;ll highlight the corresponding area in the preview.</p> <p>Click on a module in the sidebar, and we&#39;ll show you all of its options.</p> <h1>Run into trouble?</h1> <p>This is a big change, and the site builder has hundreds of features with millions of combinations of layouts and theme options. We&#39;ve done our best to avoid any regressions, but accidents happen. If you run into any trouble, be sure to reach out so we can get things patched up for you right away.</p> Improvement Pinecast is translated Matt Wed, 02 Sep 2026 11:24:00 -0000 https://changelog.pinecast.com/pinecast-translated pinecast-translated <p>Starting today, Pinecast is available in four languages other than English: <strong>Danish, French, Spanish, and Brazilian Portuguese.</strong></p> <p>From the beginning, Pinecast was built with localization in mind: we&#39;ve followed best practices for formatting text so that when we inevitably decided to launch in another language, we&#39;d be able to hit the ground running. Thanks to ten years of planning ahead, we were able to launch four new languages this month.</p> <h1>Changes to your dashboard</h1> <p>If you&#39;re an existing customer, your dashboard will probably continue showing you English text. If you&#39;d prefer to use one of the translations, you can change the language we use for your account by visiting the <a href="https://pinecast.com/dashboard/settings">Settings page</a>.</p> <p>The langauge that you set in the dashboard is the language shown <em>for you</em>. The language of your podcast is always set on the settings page for your podcast specifically, and your podcast can have <em>any</em> language, not just the ones Pinecast is translated into. Your language preference affects:</p> <ol> <li>The dashboard</li> <li>Emails you receive from Pinecast</li> </ol> <p>We do not use your language preference to identify you, and your language choice remains private.</p> <h1>Changes for your listeners</h1> <h2>Your content</h2> <p>If your podcast is in one of the languages Pinecast is translated into, you&#39;ll notice some improvements:</p> <ol> <li>We&#39;ll automatically start using the appropriate translations for text included in your show notes, like when you add a link to your Tip Jar.</li> <li>If you use our podcast websites or short links features, the text in the preview images you see when sharing a link on social media should be translated.</li> <li>The embeddable players for your show will be translated into the language of your podcast.</li> <li>Podcast websites hosted on Pinecast will show some translated text as appropriate. Note that some English text may still appear: this is likely customizable in your Site Builder.</li> </ol> <h2>Your Tip Jar</h2> <p>If you have paid subscribers who use your show&#39;s Tip Jar, they&#39;ll start seeing translated text in emails and in their tip dashboard. They&#39;ll also have the option to change their language preference after logging into the <a href="https://tip.pinecast.com">tips dashboard</a>.</p> <h1>Feedback</h1> <p>We&#39;ve done our best to translate Pinecast well, but we may have made some mistakes. If you notice any issues with the translations, please don&#39;t hesitate to reach out to <a href="mailto:support@pinecast.com">support@pinecast.com</a> to let us know.</p> <p>Also, please let us know if you speak a language that you&#39;d like to see Pinecast translated into. We&#39;re keen to expand our localization coverage in the future!</p> New