How ImageBank X Added In-Platform Photo & Video Editing in Days
ImageBank X, built by the Tampere-based software company Mediasignal, is a cloud-native digital asset management platform designed for marketing teams that want a tidy, self-service workspace rather than a heavyweight enterprise suite. Teams catalogue product shots, videos, design files, and consent forms, search them with AI-based similarity filters, and push approved assets straight into tools like Microsoft 365, SharePoint, WordPress, Shopify, and their PIM systems.
What the platform didn’t have, until recently, was a place to actually edit those assets. That gap ran on IMG.LY’s photo and video editor SDKs. Here’s how it came together, and what changed for both ImageBank X and its customers as a result.
The Challenge: Editing Lived Everywhere Except the DAM
ImageBank X started life as a lightweight cloud storage tool and grew into a full DAM through a ground-up rewrite about three years ago. As it matured, a recurring pattern surfaced in customer workflows: users would find the right asset in the library, then immediately leave to make a small change. Cropping a hero image, trimming a teaser video, swapping in the house font on a slide — all of it meant exporting the file, opening desktop software, editing, and re-uploading.
For a platform whose entire pitch is a clean, self-service workspace, that round trip was a problem. It broke the flow, it invited brand drift every time someone improvised in a tool that didn’t know the brand rules, and it undercut the “everything in one place” promise the product was built on.
Building that editing layer in-house was never realistic. Mediasignal’s engineering priorities sat squarely on the things that make a DAM trustworthy: access control, metadata governance, AI search, and integrations. A photo and video editor that could handle cropping, trimming, fonts, and layout — and do it well enough that non-designers wouldn’t notice the seams — was not where the team wanted to spend years.
I do believe that it’s critical to understand that we don’t necessarily have the manpower to do it ourselves.
The question wasn’t whether to add editing. It was how to add it without diverting the roadmap.
Why They Chose IMG.LY
ImageBank X evaluated the options against a short, practical list of requirements, and IMG.LY’s SDKs lined up against all of them.
The first was integration speed. The product is a React front-end, and the team needed an editor that would drop into that codebase quickly rather than turning into a multi-quarter project of its own.
The second was administrative control. A DAM sells trust, and trust meant the editor couldn’t be a free-for-all. Admins needed to preload the house fonts and fix logo placements so that regional teams and casual users couldn’t accidentally break the brand. The editor had to enforce the rules, not just offer them.
The third was pricing that fit a mid-market product. ImageBank X positions itself against enterprise vendors on both modernity and cost, so an editing layer that introduced per-user surprises would have undercut the whole proposition.
Customers tell us they pick ImageBank X because it feels modern and costs a fraction of the enterprise vendors.
The fourth was familiarity. Because the editor interface felt like tools people already knew, non-designers could pick it up without training, and admins could encode brand guidelines into something their teams would actually use.
Together, those four factors made the build-versus-buy math straightforward: IMG.LY delivered a richer, better-maintained editing experience than the team could have justified building, on a timeline that didn’t touch the core roadmap.
How They Implemented CE.SDK
Embedding IMG.LY’s photo and video editors into the existing React application took a few days of engineering effort — not the months an in-house editor would have demanded — and it left behind no ongoing maintenance burden. Once integrated, the editors ran entirely in the browser, so everyday edits like cropping a hero image, trimming a teaser video, or applying house fonts now happen inside the DAM instead of forcing a trip to desktop software.
The decisive configuration work was on the brand-safety side. Admins preload the house fonts and fix logo placements directly in the editor, so the rules travel with the asset. A regional marketer opening a template can move, resize, and personalize within the boundaries the brand team set, but can’t drag a logo off-grid or swap in an off-brand typeface. The constraints aren’t a checklist someone has to remember; they’re baked into the surface itself.
It’s like handing them a sandbox with the rules baked in.
With the photo and video editors in place, the team’s next step is to layer in CreativeEditor SDK for template-based PDF and print design — extending the same in-platform, brand-safe model from quick edits to full layout work.
The Results
The most concrete win shows up in a workflow as mundane as building a slide. Creating a branded PowerPoint slide used to take about fifteen minutes in desktop software, between exporting assets, placing them, and fixing the fonts. Inside ImageBank X, the same task now takes roughly two minutes. Over the span of a campaign, that gap compounds into hours saved, and it removes the temptation to improvise that produced inconsistent assets in the first place.
The placement tooling, in particular, has changed how users feel about the work.
The placement tool in the photo editor has proven to be such a useful piece of tech. Especially with consistent placement.
That sentiment is echoed by the marketing users who live in the product day to day — the people who used to spend ten minutes wrestling with where an element should sit.
The placement tool in the photo editor is so much easier. I can get it done in seconds, instead of spending 10 minutes trying to figure out placement.
The brand-consistency payoff is just as real, even if it’s harder to put a stopwatch on. Because the constraints are enforced in the editor, regional teams stopped improvising layouts, and the design drift that used to creep in across markets simply stopped happening.
Overall Impact
The most interesting result wasn’t on the production line — it was in the sales room. Editing was added to close a workflow gap, but it quickly became one of the strongest reasons prospects choose the platform.
A lot of the wow moments in demos now come from the editors.
That’s the shape of the second-order win. A capability ImageBank X deliberately chose not to build itself — embedded, brand-safe editing — turned into a primary differentiator against enterprise suites that cost far more. The engineering team kept its focus on the DAM’s core: access control, metadata, AI search, and integrations. The product gained a feature that demos sell themselves on. And the customers got back the minutes, and the brand consistency, they used to lose every time they left the platform to make a simple edit.
