Pictify Io

Generate a static image (PNG, JPEG, or WebP) from HTML/CSS content, a URL screenshot, or a template. Common use cases: Open Graph (OG) images for link previews, social media cards (Twitter/LinkedIn/Facebook), product screenshots, marketing banners, event invitations, and custom graphics. Provide ONE of: 'html' (custom HTML/CSS), 'url' (screenshot a webpage), or 'template' + 'variables' (render a saved template). Returns the hosted image URL (CDN-backed) and asset ID. Maximum dimensions: 4000x4000 pixels. IMPORTANT: The renderer captures the element's actual rendered size, not the viewport. If your HTML content is shorter than the requested height, the output image will be clipped to the content height. To ensure exact dimensions, set explicit width and height on your root element (e.g., a wrapper div) using CSS like: position: absolute; top: 0; left: 0; width: 1920px; height: 1080px; — this guarantees the element fills the full requested area.

Get details of a specific image by its UID. Returns the image URL, dimensions, format, and creation timestamp.

List what this account has rendered — images, GIFs, PDFs and videos in one feed, newest first. Filter by format, by the template that produced them, or by what called for them. Use this to find an earlier render's URL, to check whether a batch produced what was expected, or to report on recent usage. Returns each render's URL, format, dimensions, template and timestamp, plus per-format counts and a 14-day daily histogram.

List saved templates in your Pictify account with pagination and filtering. Templates are reusable HTML designs with {{variableName}} placeholders for dynamic content. Use this to discover available templates before rendering. Returns template names, IDs, dimensions, output formats, and pagination info.

Get detailed information about a specific template by its ID. Returns the template's name, dimensions, variable definitions, tags, output format, thumbnail URL, and metadata. Use this to inspect a template before rendering.

Get the variable definitions for a template. IMPORTANT: Always call this before pictify_render_template, pictify_multi_size_render or pictify_batch_render, to discover what variables are available. Returns variable names, types (text, image, color, number, boolean), default values, and descriptions. Variables support Pictify's expression engine with 50+ functions for dynamic content (e.g., IF/ELSE conditionals, string manipulation, date formatting, math operations).

Render a saved template with variable substitutions to produce an image or a PDF. This is also how you get a PDF out of Pictify: pass format: 'pdf'. For a multi-page PDF — one page per row of data, e.g. a run of invoices or certificates in a single file — pass variableSets instead of variables. WORKFLOW: 1) Use pictify_list_templates to find a template, 2) Use pictify_get_template_variables to discover its variables, 3) Call this tool with the variable values. Common use cases: OG images with dynamic titles, personalized social cards, product images with prices/descriptions, event banners with speaker info. For rendering the same template with many variable sets, use pictify_batch_render. Returns the hosted image URL (CDN-backed).

Create a new reusable template with variable placeholders for dynamic content generation. Templates can use either FabricJS canvas data (from the Pictify visual editor) or raw HTML. Provide ONE of 'html' or 'fabricJSData' — they are mutually exclusive. For HTML templates, use {{variableName}} syntax for dynamic placeholders. Pictify's expression engine supports 50+ functions: IF/ELSE conditionals, string manipulation (toUpperCase, truncate, etc.), date formatting, math operations, and more. After creating, use pictify_render_template to render it with specific values. Returns the created template's ID.

Update an existing template's content, dimensions, name, or variable definitions. Only the provided fields will be updated; others remain unchanged. You can update HTML or FabricJS data — provide one or the other, not both. Note: updating content may change the available variables.

Permanently delete a template. This action cannot be undone. WARNING: Any batch jobs or bindings using this template will stop working.

Render one template at several sizes in a single call — the same design as a 1200x630 OG card, a 1080x1080 square and a 1600x900 banner, say. Use this instead of calling pictify_render_template once per size: it is one request, one set of variables, and the results come back labelled. Different SIZES of one design; for different LAYOUT VARIANTS of it, use the 'layouts' argument on pictify_render_template instead.

Check that a template expression parses before you put it in a template. Pass the inside of the braces, not the braces: 'IF(premium, "PRO", "FREE")', not '{{...}}'. Returns whether it is valid and, if not, what is wrong with it.

List the functions available inside template expressions, with a line on what each does. Call this before writing template HTML with {{ }} logic, so the expressions use functions that exist rather than ones that look like they should.

Render one template many times — one image per row of data. Pass EITHER variableSets (rows inline) OR csvUrl with mappings (rows from a hosted CSV). Exactly one; a call with neither is rejected. Steps: call pictify_get_template_variables first to see what the template expects, call this tool, then poll pictify_get_batch_results with the returned batchId. The job is asynchronous — this returns immediately, before any image exists. Up to 100 rows per batch, plan-dependent. For a PDF rather than images, render the template with pictify_render_template and format: 'pdf'.

Check the status and results of a batch render job. Returns the job status (pending, processing, completed, failed, partial, cancelled), progress percentage, item counts, and image URLs for completed items. Each result includes index, success boolean, URL, dimensions, and error message (if failed). Call this after pictify_batch_render. If status is 'processing', call again after a few seconds to check for updates.

Cancel a running batch render job. Already completed items will retain their results and URLs. Remaining unprocessed items will be skipped. Use this if you started a batch with incorrect data or no longer need the remaining results.

List the user's video templates with their UIDs, dimensions, duration and kind. Video templates come in two kinds: 'timeline' (built in the visual studio) and 'tsx' (single-file Remotion scenes, often AI-generated). Both render the same way. WORKFLOW: call this first to find a template UID, then pictify_get_video_template_variables to see what it accepts, then pictify_render_video.

Get a video template's variable definitions — the fields you can set when rendering it (texts, colors, image URLs). Call before pictify_render_video to know what to pass.

Render a video template to an MP4 video or an animated GIF, with variable substitutions. Common use cases: personalized video messages, social video posts, animated certificates, product announcement clips, and GIFs for places an MP4 cannot autoplay (chat, email, READMEs). GIF output: timeline templates are palette-converted and capped at 15fps / 720px wide; code (tsx) templates encode GIF natively at half the composition frame rate with no width cap. WORKFLOW: pictify_list_video_templates → pictify_get_video_template_variables → this tool. The render takes up to a few minutes; this tool waits and returns the hosted file URL. Each render consumes one video credit.

Upload a Remotion scene YOU wrote as a new video template. Use when you want full creative control over the composition — write the TSX yourself instead of delegating the design to pictify_generate_video_template. The source passes a compile gate before anything is saved: on failure you get the compiler errors back and NO template is created, so fix the code and call again. SCENE RULES (violations fail the compile gate or the render): (1) Single file. It must contain `export const schema = z.object({...})` AND `export default` a React function component typed with the schema's props. Every schema field must be flat, carry .default(...), and use .describe('...') — fields become the template's editable variables. (2) Imports ONLY from 'remotion', 'react' and 'zod'. No other packages, no relative imports. (3) ALL animation via useCurrentFrame() + useVideoConfig() with interpolate() and spring(). CSS transitions/animations and Tailwind are forbidden. Always clamp: { extrapolateLeft: 'clamp', extrapolateRight: 'clamp' }. (4) Layout with <AbsoluteFill>, inline styles, system font stacks. If you use <Sequence>, it MUST carry layout="none" and integer literals for from/durationInFrames. (5) No external assets: no fetch, no hard-coded media URLs. Media only via optional string props rendered with <Img> from 'remotion'. Use remotion's random(seed), never Math.random(). (6) Never reference require, eval, dynamic import(), fs, child_process, or the word 'process' — not even in comments or identifiers.

Generate a new video template from a text prompt using AI. The service designs a motion brief (palette, beats, typography), writes the scene as code, compiles it, renders preview frames and visually reviews them — then saves a draft template whose text, colors and optional image are editable variables. Use when the user wants a NEW video design; to re-render an existing template with different values, use pictify_render_video instead. Takes 30-60 seconds and is metered as one render. Returns the template UID and a preview image URL; render it with pictify_render_video, or refine it in the studio.

Get one video template in full — its kind (timeline or tsx code), dimensions, fps, duration, variable definitions and current status. Use this before updating one, to see what is there.

Update a video template's name, dimensions, frame rate, duration, variable definitions, or — for code (tsx) templates only — its Remotion source. Only the fields you pass change. Timeline templates reject 'tsx': those are edited as a scene graph, not as code.

Copy a video template into a new one, leaving the original untouched. Use this to branch a working template before changing it. The copy counts against the saved-template limit on your plan.

Permanently delete a video template. This cannot be undone, and any automation rendering from it stops working. Renders already produced from it are unaffected.