PixelByline builds an image prompt from the site's editorial profile, visual style, post title, categories, and content summary. The free edition lets editors generate an image manually from the post editor.<\/p>\n\n
The plugin preserves editor-added featured images, supports an optional replaceable fallback image, and records recent job statuses. PixelByline Professional adds automatic generation, scheduled-post handling, reference images, retries, queue recovery, and extended activity history.<\/p>\n\n
Generated images are center-cropped to 1200 x 628 pixels and saved as AVIF by default, with WebP and PNG fallbacks. AVIF output uses the optimized source directly to avoid slow or incompatible server-side derivative generation. The post title is used for the image filename, attachment title, and alt text.<\/p>\n\n
A customer-provided OpenAI API key is required. OpenAI usage is billed directly to the customer's OpenAI account. Manual generation does not require a paid PixelByline license.<\/p>\n\n
PixelByline connects to the OpenAI API to create featured images. This service is optional, but it is required when generating an image. The site owner supplies and controls the OpenAI API key, and OpenAI bills API usage directly to that account.<\/p>\n\n
When an editor manually queues image generation, PixelByline sends OpenAI the selected model, image dimensions and quality, and an image prompt. The prompt can include the site profile and visual-style settings, the post title, categories, and a summary of the post content. The API key is sent in the request authorization header.<\/p>\n\n
When an administrator selects Test API connection, PixelByline sends the API key and selected model identifier to OpenAI to verify API access. No image is generated by that test.<\/p>\n\n
OpenAI provides this service. Use of the OpenAI API is governed by the OpenAI Business Terms<\/a> and OpenAI Privacy Policy<\/a>.<\/p>\n\n\n No. It only generates when a post has no featured image or uses the explicitly configured fallback image.<\/p><\/dd>\n Store the key in PixelByline settings. Advanced deployments can instead define Professional automation pauses and the plugin returns to Free functionality. Manual generation, existing images, posts, and settings remain available.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
Will PixelByline overwrite an editor's featured image?<\/h3><\/dt>\n
Where should I store the OpenAI API key?<\/h3><\/dt>\n
PIXELBYLINE_OPENAI_API_KEY<\/code> in wp-config.php<\/code>.<\/p><\/dd>\nWhat happens when a license expires?<\/h3><\/dt>\n
0.2.0<\/h4>\n\n
\n
0.1.6<\/h4>\n\n
\n
0.1.5<\/h4>\n\n
\n
0.1.4<\/h4>\n\n
\n
0.1.3<\/h4>\n\n
\n
0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n