By Greg Nowak. Last updated 2026-07-07.
Inline image pasting is a small Drupal feature with a real operational payoff. When editors are publishing screenshots, support notes, QA findings, product callouts, or agency handoff documentation, the difference between paste-and-continue and download-upload-insert can decide whether the CMS feels helpful or hostile.
The trap is treating image pasting as only a module question. For a current Drupal 10 or Drupal 11 site, the better question is workflow: which images should be quick inline files, which should become managed media assets, and which editor roles should be trusted with each path?
What changed
The older ckeditor_uploadimage project solved a real problem in the CKEditor 4 era. It is still useful context if you are maintaining an older Drupal 8 or CKEditor 4 build, but it is not the direction to choose for a new Drupal 10/11 setup. Its own Drupal.org page describes CKEditor 4-era requirements and currently shows no supported stable releases.
Modern Drupal work should start with CKEditor 5 in core, the text format configuration, and Media Library. That keeps the editing experience fast without allowing every pasted screenshot to become an unmanaged pile of files that nobody can reuse, audit, or replace later.
The practical model: two image paths
Most business sites need both speed and governance. Inline upload is for images that are tactical and unlikely to be reused. Media Library is for assets with a longer life: brand photography, campaign graphics, diagrams, product visuals, and anything that may appear in more than one place.
- Inline paste or drag-and-drop: best for support screenshots, temporary documentation, release notes, internal process pages, and fast editorial updates.
- Media Library embed: best for reusable assets, approved brand visuals, images that need view modes, and files that should carry consistent metadata.
| Editorial situation | Usually choose | Why |
|---|---|---|
| Support article with one-off screenshots | Inline paste | Speed matters more than reuse. |
| Homepage, campaign, or service-page image | Media Library | The asset needs governance and replacement control. |
| Agency QA notes or implementation handoff | Inline paste | Images are contextual and often short-lived. |
| Product, staff, event, or brand photography | Media Library | Metadata, reuse, and consistency matter. |
| Regulated or approval-heavy content | Media Library | Review, ownership, and lifecycle rules are easier to enforce. |
How to configure it in Drupal
Start at /admin/config/content/formats. Open the text format used by the editors who actually need this feature. Avoid enabling it broadly on every format just because the button exists.
For inline image handling, make sure the format uses CKEditor 5, add the Image button to the active toolbar, then open the Image settings and enable image uploads where appropriate. Use a deliberate file scheme and upload directory, such as inline-images, and set maximum file size and dimensions that match the real publishing use case. A screenshot workflow does not need the same limits as a photography workflow.
For governed media, enable Drupal core’s Media and Media Library modules if they are not already enabled. In the same text format, drag the Media Library button into the CKEditor toolbar and enable the Embed media filter. Put that filter late in the filter order, after filters that need to process alignment, captions, or allowed HTML first. Then test the exact field and role your editors use, not only a Full HTML format in a development environment.
Checks before you call it done
- Paste an image from the clipboard and drag a file into the editor. CKEditor 5 supports these patterns, but Drupal permissions and upload settings still decide what works on your site.
- Confirm that the saved page still contains the expected image markup after text filtering. Do not rely only on what appeared in the editor before saving.
- Check captions, alignment, alt text, and responsive image behavior against your editorial standards.
- Keep upload permissions narrow. A role that can write text should not automatically be allowed to upload files.
- Look at storage and cleanup. Inline images are convenient, but they still need backup, retention, naming, and deletion rules.
What to avoid
Do not use inline pasting for everything. If an image is part of the brand system, belongs to a campaign, or may need to be replaced globally later, put it in Media Library. Do not use Base64 image storage as a convenience shortcut for normal publishing; CKEditor’s own documentation warns that keeping the file data inside the editor output creates heavier data and transfer overhead. And do not install a CKEditor 4-era upload module on a current Drupal build unless you are deliberately maintaining legacy infrastructure.
If you are on an older Drupal/CKEditor 4 site and need short-term maintenance context, the historic Composer command was composer require drupal/ckeditor_uploadimage. Treat that as a legacy note, not a recommendation for a new Drupal 10 or 11 implementation.
A better editorial outcome
The right setup is usually a small policy backed by configuration: trusted editor formats get inline upload for fast, tactical images; reusable and approved assets go through Media Library; roles and limits are documented; and the team has a plain rule for alt text and captions.
If your Drupal editing workflow is slow, messy, or hard for a distributed team to govern, Greg can help map the right mix of CKEditor 5, Media Library, permissions, and content rules. See how Greg works as a digital project manager.
Related on GrN.dk
- AI images need a media-library audit before they reach clients
- Copy and Paste Images from the Clipboard in Drupal
- Drupal CMS 2.0 Speeds Marketing Site Rebuilds, but It Is Not Autopilot
Need help with this kind of work?
Plan your Drupal editorial workflow Get in touch with Greg.