---
type: "post"
id: "krea-launched-a-rebuilt-video-workspace-unifying-generation-0e0933"
slug: "krea-launched-a-rebuilt-video-workspace-unifying-generation-0e0933"
title: "Krea launched a rebuilt Video workspace unifying generation, editing, style transfer and sound in-browser."
description: "Krea presents a rebuilt Video workspace in its browser app for generating footage with video models and starting from an uploaded image, video, or character."
retrieval_nugget: "Krea presents a rebuilt Video workspace in its browser app for generating footage with video models and starting from an uploaded image, video, or character. The page also lists separate editing and audio tools. For teams producing AI-assisted media, this is a workflow surface to evaluate, though its precise capabilities and operating limits are not specified there."
published_at: "2026-11-06"
updated_at: "2026-11-06"
record_date: "2026-11-06"
date_kind: "published_at"
topics: ["generative-media"]
entities: ["Krea","Krea Video"]
related_patterns: ["generative-media-becomes-application-infrastructure"]
novelty_label: "new_fact"
what_changed: "Krea has rebuilt its Video workspace to bring generation, editing, style transfer and sound tools together in the browser."
prior_refs: []
source_url: "https://www.krea.ai/video"
source_urls: ["https://www.krea.ai/video"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:krea-launched-a-rebuilt-video-workspace-unifying-generation-0e0933"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/krea-launched-a-rebuilt-video-workspace-unifying-generation-0e0933/","markdown":"https://newruntime.com/posts/krea-launched-a-rebuilt-video-workspace-unifying-generation-0e0933.md","json":"https://newruntime.com/posts/krea-launched-a-rebuilt-video-workspace-unifying-generation-0e0933.json"}
markdown_url: "https://newruntime.com/posts/krea-launched-a-rebuilt-video-workspace-unifying-generation-0e0933.md"
---

# Krea launched a rebuilt Video workspace unifying generation, editing, style transfer and sound in-browser.

## Retrieval answer

Krea presents a rebuilt Video workspace in its browser app for generating footage with video models and starting from an uploaded image, video, or character. The page also lists separate editing and audio tools. For teams producing AI-assisted media, this is a workflow surface to evaluate, though its precise capabilities and operating limits are not specified there.

## Summary
Krea presents a rebuilt Video workspace in its browser app for generating footage with video models and starting from an uploaded image, video, or character. The page also lists separate editing and audio tools. For teams producing AI-assisted media, this is a workflow surface to evaluate, though its precise capabilities and operating limits are not specified there.

## What happened
Krea’s Video page describes the product as a place to “Create Hollywood grade footage” using video models. It invites users to upload an image, video, or character to make a video. The page presents this as a browser-based creation experience, but it does not name the models available within the workspace or explain how a user selects among them.

The interface groups the workflow under Video and includes a “Generate Video” mode. It displays a text field with the prompt “Tap here to generate a video...” and a “Get started” button. The page also offers an upload control for an image or video. A person can therefore begin with either a written prompt or a supplied visual asset, rather than only from text. Krea does not give a supported duration, resolution, aspect ratio, queue time, or export format, so those details cannot be treated as established features from this product page.

The surrounding Krea navigation lists Video alongside Image, Enhancer, Audio, Edit, Node Editor, Krea Agent, and other tools. The Video page names marketing, architecture, film and animation, content creation, and branding as example uses. These labels describe intended application areas, not a set of demonstrated templates or production guarantees. The page also includes a control to switch back to the classic video tool. That wording indicates an alternative older interface remains reachable, but Krea does not explain whether projects, settings, assets, or generations move between the two.

The page is an interactive product entry point rather than a detailed launch note. It supplies a generation prompt, an asset-upload path, and a category for video work, but no release date, version number, price, plan eligibility, or usage limits. Nor does it describe specific editing operations, style-transfer controls, or sound-generation steps within the Video workspace. The visible distinction matters: Krea lists editing and audio elsewhere in its product navigation, but this page alone does not demonstrate that those functions are integrated into one end-to-end video timeline.

For a builder evaluating the product, the concrete claim is consequently narrow. Krea has made Video a distinct interface in its app and positioned it around model-based generation plus uploaded inputs. Claims about a rebuilt all-in-one production environment would require product behavior or documentation beyond what the public page states.

## What the archive adds
New Runtime’s earlier coverage described Krea’s Nodes editor as a collaborative visual workflow surface where teams can co-edit graphs and invite an agent or MCP client into a project ([Multiplayer Nodes: Build Krea Workflows Together, Live](https://newruntime.com/posts/multiplayer-nodes-build-krea-workflows-together-live-e2a29a/), November 5, 2026). This is a new product-facing development, not evidence that the Nodes collaboration features are part of Video.

## Trend signal
This modestly supports [generative media becoming application infrastructure](https://newruntime.com/patterns/generative-media-becomes-application-infrastructure/): Krea is presenting video creation as one surface inside a broader suite of tools, not only as a standalone model demo. The page does not establish API availability, controllability, or production-scale integration, so the connection is about product packaging rather than proof of infrastructure readiness.

## Connections to other events
Krea’s Video surface meets an earlier New Runtime note about collaborative Nodes workflows only at the suite level. The earlier note described shared graph editing, shared runs, and the option to invite an agent or MCP client into a Krea project. The Video page does not state that any of those collaboration or agent capabilities work in Video. The connection is therefore a product-direction signal, not an integration claim.

## Why it matters
For a media team, the useful question is not whether a browser page can generate a compelling clip, but whether it fits the chain from source material to reviewable output. Krea makes the entry point legible: start from a prompt or upload an image, video, or character, then generate within a dedicated Video area. A team can assess that flow against its own brief, asset, and review process without assuming that every adjacent Krea tool is already joined into one pipeline.

That distinction helps avoid a common procurement error in generative media: treating a product suite’s navigation as proof of an integrated workflow. Separate tools for video, audio, editing, and enhancement may still require manual handoffs, different billing rules, or incompatible project states. Krea’s page makes no commitments either way. Teams should separate what they can test directly in the interface from broader assumptions about the product architecture.

The missing operational detail is consequential. Model choice, duration, export characteristics, costs, and how edits are handled determine whether a workspace can support repeatable production rather than experimentation. Until those are clear, teams should treat the page as an invitation to test the interface, not as a specification for replacing an existing video stack.

## Limits and uncertainty
Krea’s page does not identify the video models powering the experience, disclose price or usage limits, or state availability conditions. It does not quantify generation speed, reliability, output quality, or any supported media specifications. The promotional “Hollywood grade” description is not accompanied by an evaluation method, sample set, or quality benchmark.

The page also does not show whether editing, audio, or style transfer is integrated into this Video workspace. It leaves unclear whether uploaded characters have persistent identity handling, whether an uploaded video can be edited rather than merely used as an input, and whether the classic and newer tools share projects. These points would need confirmation in the product itself or in more detailed documentation before a team could estimate cost, control, and production fit.

## Skill to build now
Run a bounded workflow test rather than a visual-quality demo. Use one approved image or short source video, one prompt, and one target deliverable from an actual brief. Record the steps needed to generate, revise, export, and hand the result to a reviewer. The test should also capture what cannot be controlled or inspected in the interface, including model selection, output settings, and project handoff.

## Reader takeaway
Krea is making browser-based video generation more discoverable as part of its creative suite, with uploads and a path back to the classic tool. That is enough to justify a hands-on check for teams exploring AI video, but not enough to infer a unified editing pipeline, named model support, or production economics. Verify those details in the workspace before building a workflow around it.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Generative Media](https://newruntime.com/topics/generative-media.md): Explore the generative-media topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)