Where Portwood
is headed.
Up next, on the horizon, and still being explored. Free forever, community-driven, and tracked in the open — this page mirrors the roadmap file in the source repo, so it says the same thing to you as it does to the people building it.
The question behind the roadmap is “will this still be here?”
Fair question to ask of free software before you put it in front of your customers, so here are the numbers rather than a reassurance. And the real answer isn't any of them: Portwood is Apache 2.0. The version in your org is licensed to you irrevocably. If we stopped tomorrow, your documents keep generating and anyone can fork the source — which is a guarantee no paid vendor in this category can offer you.
- Current releasev3.56.0
- Shipped8 Aug 2026
- Releases since v3.051
- Automated tests1,961
- LicenceApache 2.0
Portwood is free, native, and community-driven. There are no paid tiers and no feature gates, so this roadmap isn't a sales sheet. It's an honest view of what's queued and what we're still thinking about. Priorities come from real customer reports and community requests, triaged in the open on GitHub — the issue board is the source of truth for what's in flight.
Portwood is listed on the AppExchange and ships on a fast release cadence — currently v3.56, with 51 releases since v3.0 in May 2026. Recent releases brought the Canvas designer (Beta), element linking and named blocks, client-side charts, Excel output as real .xlsx, and the runner on any page. For the full record, see the changelog.
Want to shape it? Open a request on GitHub Issues or post in Slack. Every request gets read, labeled, and tracked. Bugs that silently corrupt output jump the queue.
Up next
Up next4 itemsEnhancements with a clear path, planned for the next release or two.
Preview before you save (#212)
The runner generates and saves in one step. This adds a preview (and print) of the generated PDF before you commit to saving it on the record or downloading it — catch a wrong template or a bad merge before it becomes a File.
Template comments (#211)
A comment syntax for template authors: leave notes to yourself ("this table feeds from the Opportunity line items") inside the template, and the merge engine strips them from every generated document.
Custom Label merge tags (#204)
Resolve Salesforce Custom Labels inside templates, so one template can serve a multi-language org — the label renders in each recipient's language instead of hardcoded text.
Canvas designer out of Beta (#55)
The drag-and-drop template builder shipped in v3.54 as a Beta: a Canva-style artboard where boxes are placed in inches and land there in the PDF, with lists still flowing across as many pages as the data needs. Word and HTML templates remain fully supported and are still the right choice for many documents — the Canvas is an additional authoring path, not a replacement. Hardening it to general availability is paced by what early users hit, so feedback on this one is worth more than a vote.
On the horizon
Planned3 itemsLarger items on the list, paced by community demand.
Images in signature and notification emails (#198)
Logos and branding images in the emails Portwood sends around signing and delivery. Weighing two designs — routing through the shared asset system versus a public-URL hook — before committing.
Bulk runner and admin in every language
The document runner already follows each user's Salesforce language across ten translations (Spanish, Japanese, Chinese, French, German, Portuguese, Italian, Korean, Dutch). The bulk-generation and template-admin screens are next, so the whole app speaks the user's language without a separate setting.
Right-to-left line wrapping
Long right-to-left paragraphs that wrap can start their continuation lines from the wrong margin, a limitation of the PDF engine's bidirectional text support. (The signing preview and final PDF render RTL text correctly today.) On the list for a future release.
Exploring
Exploring3 itemsIdeas with merit that are iceboxed until demand moves them up. Feedback here is especially useful — a few voices asking is what promotes these.
Reusable template partials (#31)
Define a header, footer, or signature block once and include it across many templates. A design spec is drafted; it's iceboxed until enough teams ask for it.
Native, editable Office charts
Portwood charts render as crisp images today — they look right in every format, but you can't click into them in Word or PowerPoint to change the underlying numbers. A future direction is emitting native Office chart objects so recipients can open Edit Data and adjust the chart directly. Image charts would stay the default; this would be an opt-in for Office-native output.
PDF export from Excel and PowerPoint
Excel and PowerPoint templates currently generate in their native formats only, while Word and HTML can also produce PDF. Extending the PDF path to spreadsheets and slide decks is on the list, paced by demand.
How we prioritize
ProcessEverything is triaged in the open. Each issue gets a priority label:
- P0 — output is silently wrong, there's data loss, or the package is unusable for a whole segment. Ships in the next dot release, no exceptions.
- P1 — a visible bug or regression with a workaround, or impact scoped to one feature. Planned into the next release or two.
- P2 — a planned enhancement that's specced and actionable.
- P3 — backlog. The idea has merit but needs more scoping, or impact is lower. Revisited as capacity allows.
Silent corruption always outranks loud crashes: a bug a customer can't see they hit beats a noisy error every time. Releases ship on a rolling set of milestones, and the backlog is re-evaluated each time one is cut.
> This roadmap is a direction, not a contract. Dates aren't promised, ordering can change, and community demand moves things up. For the definitive record of what actually shipped, see the changelog.
Mirrored from ROADMAP.md in the source repo, and refreshed live when you open this page. Plain text at /roadmap.md. A direction, not a contract — for what actually shipped, see the changelog.
Have something to add?
Portwood is built on what the community asks for. Request a feature, report a bug, or just tell us what would make your week. Every request gets read and tracked — and none of it costs anything.
Need something in your org rather than in the product? That's Premium Support — or if you're weighing a move off a paid vendor, start with how migration works.